std::priority_q ueue derivable?

[red floyd]

I know it's generally bad from to derive from STL containers. That
said, here's my question:

I am using std::priority_q ueue<>. However, I need to be able to access
the underlying container; specifically, I need to be able to get at
begin() and end() for it.

Josuttis (10.3.3) shows that the compare operator and the container are
*protected* members of std::priority_q ueue. This would lead me to
believe that it was intended for derivation. I was thinking about doing
something like this:

class my_data { /* contents redacted */ };
class my_priority_que ue : private std::priority_q ueue<my_data>
{
public:
typedef std::priority_q ueue<my_data> pq;
using pq::top;
using pq::push;
using pq::pop;
using pq::empty;
using pq::size;
my_priority_que ue();
~my_priority_qu eue();
void do_something_to _all_elements() ; // uses c.begin() and c.end()
};

Is this kosher?

[Gianni Mariani]

red floyd wrote:

I know it's generally bad from to derive from STL containers.
It's fine to derive from STL containers.

That said, here's my question:

I am using std::priority_q ueue<>. However, I need to be able to access
the underlying container; specifically, I need to be able to get at
begin() and end() for it.

Josuttis (10.3.3) shows that the compare operator and the container are
*protected* members of std::priority_q ueue. This would lead me to
believe that it was intended for derivation. I was thinking about doing
something like this:

class my_data { /* contents redacted */ };
class my_priority_que ue : private std::priority_q ueue<my_data>
{
public:
typedef std::priority_q ueue<my_data> pq;
using pq::top;
using pq::push;
using pq::pop;
using pq::empty;
using pq::size;
my_priority_que ue();
~my_priority_qu eue();
void do_something_to _all_elements() ; // uses c.begin() and c.end()
};

Is this kosher?

In theory, this should work, however a (in)famous C++ compiler does not
accept this. (MSVC). To work around it, I redefine the methods inline
in the dervied class.

[red floyd]

Gianni Mariani wrote:

red floyd wrote:

I know it's generally bad from to derive from STL containers.

It's fine to derive from STL containers.

That

said, here's my question:

I am using std::priority_q ueue<>. However, I need to be able to
access the underlying container; specifically, I need to be able to
get at begin() and end() for it.

Josuttis (10.3.3) shows that the compare operator and the container
are *protected* members of std::priority_q ueue. This would lead me to
believe that it was intended for derivation. I was thinking about
doing something like this:

class my_data { /* contents redacted */ };
class my_priority_que ue : private std::priority_q ueue<my_data>
{
public:
typedef std::priority_q ueue<my_data> pq;
using pq::top;
using pq::push;
using pq::pop;
using pq::empty;
using pq::size;
my_priority_que ue();
~my_priority_qu eue();
void do_something_to _all_elements() ; // uses c.begin() and c.end()
};

Is this kosher?

In theory, this should work, however a (in)famous C++ compiler does not
accept this. (MSVC). To work around it, I redefine the methods inline
in the dervied class.

Thanks. I guess that it's MSVC6 that doesn't like it. MSVC7.1 does,
as does g++ 3.2.2