Hello,
Last year, a colleague and I ported Xerces-C++ 1.4 to Alpha OpenVMS 7.3
in order to use it with the Computer Associates' Ingres release 2.6 on
that platform. Aside from the Xerces 1.4 sources, we used a simple
"compile all" script from the HP port of Xerces 1.3, publicly available
at their site. We made the following changes:
src/util
AutoSense.hpp Replacement to add Alpha VMS detection
TransService.hpp Replacement to add DEC MCS transcoder
(MCS = Multinational Character Set)
XML88591Transcoder.cpp Minor correction
XMLDECMCSTranscoder.cpp Addition
XMLDECMCSTranscoder.hpp Addition
XMLUni.cpp Replacement to add MCS encoding
XMLUni.hpp Replacement to add MCS encoding
XercesDefs.hpp Replacement to add Alpha VMS defines
src/util/Compilers
DECCXXDefs.hpp Replacement to change typedef for XMLCh
Now I need to port Xerces-C++ 2.5 to Alpha OpenVMS in order to use it
with Ingres r3. In addition to the change from a commercial to an open
source release, Xerces has taken added importance within Ingres. In
release 2.6, it was only used for utilities to import and export data in
XML format. It is now used by the Ingres DBMS itself to support coercion
between Unicode and non-Unicode data.
I have two questions for Xerces developers. First is whether it would be
at all useful to contribute the 1.4 file changes, so that they can be
branched or merged into subsequent releases. Second, assuming the answer
is no, is it OK to submit the comparable changes to 2.5, notwithstanding
the fact that 2.6 is the current release? I looked for some policy
statement that would guide submission to earlier releases, but could not
find one.
Thanks.
Joe Abbate
Computer Associates
Senior Software Engineer
+1 786 709 2002
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
