James Murphy <[EMAIL PROTECTED]> wrote:
> This was the issue I was looking for. Currently if I try to include
Xerces
> and Xalan headers I get a name collision in QName.hpp. If this rename
could
> simplify the usage of BOTH Xerces and Xalan together I'm in.
This had been fixed in the latest Xalan release, which is currently being
uploaded to the Apache server even as I write this message...
> While were on the subject of upsetting apple carts -
>
> I would also like to change the include file convention to use quotes
> instead of angle brackets. In this way I wouldn't have to modify my
include
> path at all for any of my projects! Everything would work relative to
each
> file (something the preprocessor wont do if you use <> to include)
The behavior of <> vs. "" is defined by the C++ standard as
implementation-specific, so it may "work" for your particular compiler, but
it might not work the same way on a different one. Do you really want to
rely on that?
Dave
"Murphy, James"
<James.Murphy@exce To: "'[EMAIL PROTECTED]'"
lergy.com> <[EMAIL PROTECTED]>
cc: (bcc: David N Bertoni/CAM/Lotus)
08/17/2001 10:55 Subject: RE: Changing include to
include/xercesc
AM (What about Xalan?)
Please respond to
xerces-c-dev
This was the issue I was looking for. Currently if I try to include Xerces
and Xalan headers I get a name collision in QName.hpp. If this rename
could
simplify the usage of BOTH Xerces and Xalan together I'm in.
While were on the subject of upsetting apple carts -
I would also like to change the include file convention to use quotes
instead of angle brackets. In this way I wouldn't have to modify my
include
path at all for any of my projects! Everything would work relative to each
file (something the preprocessor wont do if you use <> to include)
The I would add my own header that included xerces,xalan and friends.
Jim
> -----Original Message-----
> From: Paul Emberson [mailto:[EMAIL PROTECTED]]
> Sent: Friday, August 17, 2001 10:40 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Changing include to include/xercesc (What about Xalan?)
>
>
> Currently xalanc and xercesc have the same file hierarchy.
> Surely for
> consistency you'd have to change xalan as well. It would
> make sense to do
> it all at the same time.
>
> Paul
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
