Paul Black wrote:
> Why not:
> class SomeClass
> {
> public:
> SomeClass();
> // more stuff...
> protected:
> struct mylist_t {
> mylist_t *next;
> void *dataM
> };
> };
Then I cannot use
SomeClass::mylist_t *list
but I would have to use
struct SomeClass::mylist_t *list
which is ugly and this is why I had the typedef in the first place.
I just wonder if this is indeed the intended behavior, typedef are not
allowed as members, or if this is just a bug. If its the former I'd like
to now what the rationale is behind this...
Any more ideas?
Tim
--
Tim Niemueller <tim@xxxxxxxxxxxxx> www.niemueller.de
=================================================================
Imagination is more important than knowledge. (Albert Einstein)
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
