Re: Changing include to include/xercesc - Summary and Vote

[J. J. Merelo]

-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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]