> - I wonder why there is no something like IstreamInputSource
>
We always very clearly kept all of that stuff out of the parser, so as to
avoid having to be dependent on it. If someone were to want to use the
parser in some low memory situation, we don't want to bring along any more
baggage than
On Tue, Jun 12, 2001 at 04:03:01PM -0700, Dean Roddey wrote:
> It seems like people are getting kind of sloppy about include statements. I
> see a number of includes in the DOM that are in the form "xxx.hpp". This
> won't work in build systems which don't include the original source tree in
> the
[mailto:[EMAIL PROTECTED]]
Sent: Tuesday, June 12, 2001 4:03 PM
To: '[EMAIL PROTECTED]'
Subject: Some include issues
It seems like people are getting kind of sloppy about include statements. I
see a number of includes in the DOM that are in the form "xxx.hpp". This
won't wo
It seems like people are getting kind of sloppy about include statements. I
see a number of includes in the DOM that are in the form "xxx.hpp". This
won't work in build systems which don't include the original source tree in
the include path, i.e. they build out of tree. I believe that they should
