On 7/14/05, Larry Battraw wrote: > From a little more digging it looks like it's due to problems with > ordering/scope. For example, the first error for "SegmentToolBox* > getToolBox();" (line 83 of segmenttool.h) goes away once the prototype > (?) is moved below the actual definition on line 97. I'm guessing the > compiler doesn't know what SegmentToolBox is until the definition. > Why this would work for gcc/g++ 3.x and not now seems odd. Things get > much more involved when the next errors pop up in > qcanvasgroupableitem.h; the definitions make references between > sections and moving one tends to break the other.
Perhaps there is a clue here: http://gcc.gnu.org/gcc-4.0/changes.html Quote: When declaring a friend class using an unqualified name, classes outside the innermost non-class scope are not searched: class A; namespace N { class B { friend class A; // Refer to N::A which has not been declared yet // because name outside namespace N are not searched friend class ::A; // Refer to ::A }; } Hiding the friend name until declaration is still not implemented. Regards, Pedro ------------------------------------------------------- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
