Identifiers can't be keywords. On the other hand, my copy of the 1997 C++ Public Review Document doesn't include 'export' as a keyword.
Regards, Eric Ulevik From: <[EMAIL PROTECTED]> > 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. > > Keith Bisset <[EMAIL PROTECTED]>@rhapsody.lanl.gov on 01/19/2000 01:40:39 PM > > 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.
