RE: Changing include to include/xercesc

["Hespelt, Steve (Exchange)" <sh...@bear.com>]

I don't understand the last sentance. there is potential namespace
collisions regarding headers that may be included by xerces code. So my app
code may not cause an include file collision (with some other library) but a
xerces header file could. How could the xerces developers know which header
files (with path prefix) might clash with other libraries? Make the xerces
directory part of the path prefix in every #include statement to minimize
such collisions.

> -----Original Message-----
> From:	J. J. Merelo [SMTP:jmerelo@geneura.ugr.es]
> Sent:	Friday, August 17, 2001 11:13 AM
> To:	xerces-c-dev@xml.apache.org
> Subject:	Re: Changing include to include/xercesc - Summary and Vote
> 
> -1
> 
> > 1.  It helps addressing the name collisions between header files from
> various libraries that, unfortunately(but realistically), have the same
> names.  Different products (3rd party or user applications) can
> > also have e.g. <util/Base64.hpp> or <util/Mutexes.hpp>.  So, why not
> have the Xerces include paths start with <xercesc/...> which makes things
> more obvious and can help avoid some problems.
> 
> Those can be addressed individually, on a file-by-file basis.
> 
> J
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
> For additional commands, e-mail: xerces-c-dev-help@xml.apache.org


****************************************************************
Bear Stearns is not responsible for any recommendation, solicitation, 
offer or agreement or any information about any transaction, customer 
account or account activity contained in this communication.
***********************************************************************


---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org