"David N Bertoni" wrote:
> Well, that's imposing something on C/C++ which is not defined by the
> standard, so I don't know whether I agree with that behavior or not. Are
I don't know what the standard says on the issue, but Stroustroup
is clear about the difference between ""'s and <>'s with #include
in The C++ Programming Language, 3ed, Sect 9.2.1 (p. 201). I
wouldn't think the Standard disagrees with him (although I can see
it leaving it implementation-dependent since a hierarchical file
system is outside the scope of the language definition).
"Jason E Stewart" wrote:
> should be referenced by double quotes. Perhaps windows doesn't care,
> but unix does.
Actually, Microsoft Windows cares, too. I think it is standard (or,
see above, if it's not standard, it is Bjarne).
"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.
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.
Instead, it is better to think of Xerces-C as a 'library component'.
To "plug the component in," set -I and the appropriate LIBPATH
or path to the import lib on Microsoft Windows (and any environ-
ment required on UNIX for make) and it should be located from
wherever your projects may build from.
Derek Harmon
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
