Before submitting the changes, how about just giving everyone a discussion
of what was required to make it work. This would give us a chance to
comment on what you've done and, if we feel something needs to be changed
before accepting it, that you can make those changes and test them out
before submitting.
On the subject of the mixed signed/unsigned stuff, yes those are being
removed as time goes by. I think that most of them are gone in the current
code base. And, BTW, what code base have you been working against? We'd
definitely want any submitted changes to be against the most recent code
base.
----------------------------------------
Dean Roddey
Software Weenie
IBM Center for Java Technology - Silicon Valley
[EMAIL PROTECTED]
Gary Gale x58814 GB- COM/Q/6th <[EMAIL PROTECTED]> on 03/13/2000
03:23:32 AM
Please respond to [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc:
Subject: Xerces-C on Tru64 - An Update and Some Questions
A while back (the end of January if I recall) I posted to this list to see
whether anyone was porting, or considering porting, Xerces-C onto Compaq
Tru64
(aka Digital Unix).
Thanks to all who responded, even if it was to say that Tru64 was an
unsupported platform.
I've now got to the stage where I can build Xerces-C, plus the sample apps,
on
Tru64 4.0f using DEC C++ V6.2. As a result of this some questions, both
legal
and code-wise have come up
1) Compiling Without Warnings.
These are several places throughout the code where a variable, explicitly
declared as unsigned is assigned/compared to a signed value. For example,
in
src/internal/XMLScanner2.cpp we have this code fragment
const unsigned int colonOfs = XMLString::indexOf (attrName, chColon);
if (colonOfs != -1)
{
...
}
Quite rightly, the DEC C++ compiler complains about this with the
diagnostic
cxx: Warning: XMLScanner2.cpp, line 1001: integer conversion resulted in a
change of sign
Likewise, there are also unreachable statements in several places which
have
obviously been put in to keep other compilers happy but DEC C++ winges
about
"statement is unreachable".
I don't want to put conditional code into supposedly platform independent
code
just to keep one compiler out of many happy but I do want the code to build
warning free. Any suggestions?
2) Submitting the Port
