At this point we would probably only be interested in those mods for the
new 1.1.0 base. Perhaps some other foks might want to have access to your
work for the 1.0.1 stuff, but we are now up to 1.1.0 and would want to
check in projects against that. In fact, I think we have checked in some
new projects against that, so you might want to update and see what the
state of the state is now. The new version is FAR better.
----------------------------------------
Dean Roddey
Software Weenie
IBM Center for Java Technology - Silicon Valley
[EMAIL PROTECTED]
Eric Cloninger <[EMAIL PROTECTED]> on 03/09/2000 08:12:59 AM
Please respond to [EMAIL PROTECTED]
To: <[EMAIL PROTECTED]>
cc:
Subject: Newbie comments and questions
Hello all,
I'm new to the list, so please forgive me if I say or ask something
stupid...
* I'm using Xerces 1.0.1 for my project. My project builds on the Mac
using
Metrowerks CodeWarrior Pro 5.3 and Windows using CodeWarrior and VC++. The
CodeWarrior projects included with the Xerces distribution are out of date
and aren't cross platform. Is there someone I should work with to get my
mods back into the base (assuming they are wanted)? Until recently, I
worked for Metrowerks, so I think my mods would be useful to other
CodeWarrior users.
* Is there a requirement that Xerces run as a DLL/shared library? I've
modified the code to run as a static library and would prefer to ship it
that way.
* I have a crasher that occurs in DTDElementDecl::createChildModel(). The
offending code is
const ContentSpecNode* specNode = getContentSpec();
if (specNode->getElemId() == XMLElementDecl::fgPCDataElemId)
ThrowXML(RuntimeException, XML4CExcepts::CM_NoPCDATAHere);
The crash occurs because specNode is NULL. In my case, the user input is
definitely incorrect, but I don't expect to crash as a result. I'm
beginning to put my 1.0.1 mods into 1.1.0 to see if it fixes the problem,
but I'm skeptical since I don't see any changes in this file or the three
functions up the call stack.
I'm not familiar with the internal operation of Xerce, so can someone
comment whether a test for NULL should be inserted in this code or whether
it's unreasonable to expect to encounter this situation?
Thanks
-E
