Is it true that if there is a keyword 'bar', then you cannot create a
method 'foo::bar', within the scope of a class? That doesn't seem very
logical, though it could well be correct, since no one said it had to be
logical I guess. None of the other compilers complain about this, and you'd
think that (between all the compilers we support), that if it were really
wrong they would complained.
I guess we can rename this if we have to, but I'd like to know if anyone
knows for sure what the correct answer is to this.
----------------------------------------
Dean Roddey
Software Weenie
IBM Center for Java Technology - Silicon Valley
[EMAIL PROTECTED]
Keith Bisset <[EMAIL PROTECTED]>@rhapsody.lanl.gov on 01/19/2000 01:40:39 PM
Please respond to [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc:
Subject: Problem compiling with GCC
There is a problem compiling Xerces with gcc 2.95.2. According to the
standard, export is now a C++ keyword. The following files use export
as a function name.
src/dom/DocumentImpl.cpp
src/dom/DocumentTypeImpl.cpp
src/dom/DocumentTypeImpl.hpp
src/dom/NamedNodeMapImpl.cpp
src/dom/NamedNodeMapImpl.hpp
Once I changed export to Export, everything works ok. I expect that
this will be a problem as more compilers are changed to match the
standard.
Keith Bisset
