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

[Murray Cumming]

"J. J. Merelo" wrote:
> 
> -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.

Please elaborate on this last sentence.

> J
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]

-- 
Murray Cumming
www.murrayc.com
[EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]