On Tue, Jul 05, 2005 at 07:37:58PM -0700, Larry Wall wrote:
> I think I'd rather see a :lang('tcl') option since :c is taken and
> :l isn't. But mostly people will want to put
> use rule :lang<tcl>;
> or some such at the beginning of the file, since all the rule actions
> are likely to be in the same language.
Fair enough. :-)
> : Anyway, if this is really chasing down a dead-end, just say so and
> : we'll go with the other approach. But I feel like it simplifies things
> : a lot (both for PGE and for compiler authors) if we can have a
> : generalized code block delimiter available.
>
> We need to pursue both options. Languages with left-to-right parsers
> aren't going to want to put {{...}} everywhere.
Agreed; I was looking for an additional option as opposed to a
replacement.
> I'd lean more toward the infinitely extensible PODly technique:
>
> {...}
> {{...}}
> {{{...}}}
> {{{{...}}}}
This is very fine with me, except I'm guessing that the {...} form
(single curly brace) probably needs to call the language parser to
find the end and not simply stop on the first closing curly brace
encountered. But the others seem to be just fine, and I'll write
PGE that way for the time being.
Pm
