Another reason not to use the standard libs. We very purposefully try to
keep the extensions disabled becasue most of the development is done in the
Win32 environment. If we don't do this, I will end up checking in code that
is not compliant and breaks on other compilers. I know its MS' fault, but I
still would prefer to be able to keep strict ANSI on. If DOMString were be
replaced like this, anywhere that DOM was visible would have to turn off
strict ANSI checking.
----------------------------------------
Dean Roddey
Software Weenie
IBM Center for Java Technology - Silicon Valley
[EMAIL PROTECTED]
[EMAIL PROTECTED] on 01/13/2000 04:31:08 PM
Please respond to [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc:
Subject: Re: DOMString (was: xalan-c Problem with Xerces initialization)
Yes, that reminds me... I impaled myself on those cryptic error messages
for quite a while, before I figured out that VC++ can't process the
standard header files if you have "Disable language extensions" turned on.
Just click it off on the C/C++ / Customize tab. Go figure...
Curt Arnold wrote:
>I've just started trying trying to identify issues to morphing DOMString
>into std::basic_string semantics. I'm running into a little wacky behavior
>in the VC6 IDE build that maybe someone will recognize off the top of
their
>head. I'm using the 1_0_1 drop, debug build, on VC 6 SP2. If I add a file
>to the XercesLib subproject (test.cpp) that is simply
>#include <string>
>std::basic_string<char> test;
>And build in the IDE, I get a slew a error messages starting with
>d:\msdev6\vc98\include\utility(81) : error C2146: syntax error : missing
';'
>before identifier 'iterator_category'
> d:\msdev6\vc98\include\utility(84) : see reference to class
template
>instantiation 'std::iterator_traits<_It>' being compiled
