Hi,

Comments are inline.

"christopher diggins" <cdiggins@videotron.ca> wrote in message news:cvvgi0$1an$1@digitaldaemon.com...
> Hi ZZ,
>
> I really appreciate your feedback, and involvement!

thanks.

> Concerning the large file parsing issue, what would be require would be
for
> someone to write a custom ParserInput type (see http://www.ootl.org/yard/#parser ). I haven't written a file reading input type which uses fread, as I think it may be outside the scope of the library. I don't know how hard it is for others to fill in the gaps. Would you be willing to write an efficient file reading type and share it with
us?

The method we use is a subset of the on metioned in a paper by Waite in '86 "The cost of Lexical analysis", the same method but a little bit different is used in LLC compiler for the lexical analysis and is documented in their book "A Retargetable C Compiler: Design and Implementation" the sample chapter they give online actually describes this section http://www.cs.princeton.edu/software/lcc/doc/06.pdf

The same method for reading is also used in Boost WAVE when compiled with the  WAVE_USE_RE2C_CPP_LEXER option, this Lexer is fast fast fast and can beat hand rolled lexers.

boost  xpressive was supposed to be at least on par with re2c when completed and it would generate a statically bound lexer for Spirit or be used alone.

> Unfortunately I could not read the rdp documentation (no post-script reader). I could not understand the examples you shared with me.

you can download ghostscript to read the documents.
(postscript is one of the things we parse).

> Let me know whether you can get the yard examples working. Thanks!

I'll try them out with CodeWarror soon.

Zz.