[xml/sgml-pkgs] Bug#245368: no, it is a xerces problem after all
Jay Berkenbilt <email@example.com>, firstname.lastname@example.org
Fri, 21 May 2004 00:30:16 GMT
See bug 249691 for details -- I was wrong; this is not a gcc bug. g++
3.4 is complaining about an incorrect construct that gcc 3.3 accepted
After xerces24 hits unstable (should be any day now), I'll make sure
xerces23, xerces24, and xerces25 all compile with gcc 3.4 and will
report any problems upstream (for xerces25) in addition to creating
new versions of these packages.
Thanks for your report. I hadn't been previously aware of gcc-3.4 in
experimental until this report prompted me to go looking for it.
Rather than using your patch as submitted, I'm going to favor
qualifying the unqualified name with this-> since it avoids hardcoding
the fact that the name comes from the base class. Either way, the
next version of xerces2 will compile with gcc 3.4.
Jay Berkenbilt <email@example.com>