"Peter A. Volchek" wrote:
>
> > Here's my previous post again, for those who missed the reasoning:
> >
> > Murray Cumming wrote:
> > >
> > > I'd like to rename the 'src' directory to 'xercesc'. Here's why:
> > >
> > > I recently changed the build files so that they install the headers
> > > under a <prefix>/include/xercesc directory instead of polluting
> > > <prefix?/include with all of the generically-named xerces-c sub dirs. I
> > > had a secondary aim - to make it more obvious when client code #includes
> > > xerces-c headers.
> > > e.g.
> > > #include <xercesc/framework/MemBufInputSource.hpp>
> > > is a lot clearer than
> > > #include <framework/MemBufInputSource.hpp>
> > >
> > > The problem is that the xerces-c header files don't use this method, so
> > > you need 2 include directives when compiling your code:
> > > e.g. -I/home/mcumming/include -I /home/mcumming/include/xercesc
> > >
> > > To fix this, I'd like to add the 'xercesc/' bit to the includes in all
> > > the xerces-c header. BUT, then xerces-c wouldn't build because the
> > > headers are actually in src. SO, let's rename that directory. This
> > > technique is used by lots of libraries, such as gtk.
> >
> >
> > --
> > Murray Cumming
> > www.murrayc.com
> > [EMAIL PROTECTED]
> >
>
> When are you going to make the changes ? Could them wait till next Xerces
> release?
> You'd better concentrate on such a vitally important things like full Schema
> support (group, all, list, union)
> Just my opinion.
So we shouldn't fix something that's straightforward to do because there
are other more complex things that haven't been fixed yet? Sorry, that
does not compute.
--
Murray Cumming
www.murrayc.com
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
