"Arnold, Curt" wrote:
>
> I haven't been following this thread and it troubles me that appears that it would
>require touching every single include of a Xerces header file at least in
>applications (and possibly in the Xerces
> code base itself)?
No, I have said several times that this will not require any existing
apps to change the way that they #include the Xerces-C++ headers. Read
the thread.
And I don't see the point in complaining that it will be necessary to
change part of the Xerces-C++ code base. Of course it needs to be
changed to be fixed.
>
> And the problem seems pretty vague, at least to a (primarily) Windows developer.
Yes, it's not important to Windows developers because header files are
not installed on Windows systems, and because Windows developers have
the responsibility for installing dependencies during the installation
of their applications.
However, until we fix the build issues then Xerces-C++ will:
- Never be easy to install.
- Never be provided with Linux distributions.
So if your unix app uses Xerces-C++ then it might never be used because
each user needs to:
- Download a 6mb tar.gz.
- Figure out how to install it.
At the moment that is a very sad situation because Xerces-C++ is
otherwise wonderful code. And I don't know of any alternative C++ XML
parsers.
> If the problem is a conflict with similarly named include files on *nix, couldn't
>you achieve the same result by
> setting up a Xerces directory with symbolic links to all the appropriate
>subdirectories and not need to touch the actual file locations.
>
> Anything that makes it difficult for me to build an app against the Xerces source
>tree or a binary release without code changes, doesn't sound like a good thing.
1. You will not have to do any more work than you already have to do for
each new Xerces release. I have made that clear.
2. It's stupid to say that all change is bad.
--
Murray Cumming
www.murrayc.com
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
