> > "Murphy, James" (The Original Poster) wrote:
> > 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)
>
> If you install Xerces underneath _each_ of your projects, maybe that
> looks like a good idea to you. However, many developers install it
> in one place, and refer to it from multiple projects scattered across
> their workstation in whatever organization they want.
Ya I know - that's the way I would like to do it too but that's not how its
done here. We want it to be included by project/makefile only not using
environment variables. I would like to include all the Xerces headers my
application uses like this:
... in MyXerces.h... a header located in out common include directory, above
Xerces-c
#include "Xerces-c/util/XMLUniDefs.hpp"
#include "Xerces-c/util/XMLUni.hpp"
#include "Xerces-c/util/PlatformUtils.hpp"
#include "Xerces-c/framework/URLInputSource.hpp"
#include "Xerces-c/framework/MemBufInputSource.hpp"
#include "Xerces-c/framework/XMLPScanToken.hpp"
#include "Xerces-c/parsers/SAXParser.hpp"
#include "Xerces-c/sax/AttributeList.hpp"
#include "Xerces-c/sax/HandlerBase.hpp"
#include "Xerces-c/sax/ErrorHandler.hpp"
#include "Xerces-c/sax/SAXParseException.hpp"
#include "Xerces-c/parsers/DOMParser.hpp"
#include "Xerces-c/dom/DOM_Document.hpp"
#include "Xerces-c/dom/DOM_Element.hpp"
#include "Xerces-c/dom/DOM_Node.hpp"
#include "Xerces-c/dom/DOM_NamedNodeMap.hpp"
#include "Xerces-c/dom/DOMString.hpp"
all my applications that use Xerces simply includes MyXerces.h instead of
sprinkling their code with little bits or Xerces header includes. That way
when you guys decide to change the directory structure I change 1 file
instead of hundreds. :) This is thwarted now because my applications
require the xerces-c directory in their include path since the headers
include other headers using the <> notation.
> It would end up changing every #include potentially for each project,
> and if we decided to distribute with something like:
>
> #include
> "..\..\..\projects\Apache\Xerces\Cxx\DOM_DocumentImpl.hpp"
>
> 99% of the developers in the world would be most cross with us because
> that doesn't fit with their project layout.
Oh nasty - I was certainly not advocating this. Just global search and
destroy <> with "". The Xerces projects would remain unchanged and require
whatever include path additions.
Jim
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
