Re: coupling LALR with a scanner?

"Armel" <armelasselin@hotmail.com> writes:


>> there is an argument for introducing such a gap to "segment"
>> tokens into smaller chunks for both performance and expressibility
>> reasons.
>
> could you elaborate on this segmentation mechanism?


I would like to, but the idea is going through the patent process, as
it has hardware design implications. Once I know that the patent has
been filed, or get other ok from Intel legal, I will write the idea
up.


> In my lexer generator, the developer can introduce start states by himself
> and 'cut' complex expressions into smaller expressions which still respect
> AFD capabilities and introduce dynamic regular expressions where absolutely
> necessary, for languages allowing dynamic string delimiters for example
> (e.g. doc-strings like << END_OF_STR_MARKER, some lines then a line with
> END_OF_STR_MARKER only on the line), languages such as ruby are very funny
> from that point of view if I remember well.


Those sound like useful extensions. In the hands of an experienced
parser writer, that could make the process much easier. Let the
system figure out what it can, then adjust where you must.

Return to the comp.compilers page.
Search the comp.compilers archives again.