At 06:40 PM 4/24/2001 -0500, David L. Nicol wrote:
>Dan Sugalski wrote:
> >
> > [BTW, was this meant to be CC'd to one of the perl 6 lists? My copy wasn't]
>
>yeah, I have perl6-language as a alias but not "language" by itself
Fixed.
> > At 05:55 PM 4/24/2001 -0500, David L. Nicol wrote:
> > >Dan Sugalski wrote:
> > >
> > > > Most of the parser switching is going to be of the nesting variety.
> Every
> > > > time the parser processes a double-quoted string constant or a regular
> > > > expression you're going to be jumping parsers. That's all
> temporary, and we
> > > > really do want them to nest. (You really don't want the perl parser
> to lose
> > > > all its state every time you start a string...)
> > >
> > >No, of course not. I'm asking for separation of "parsing" and "state"
> > >so that multiple parsers can cooperatively contribute to the developing
> > >state. That is what would be required for python mode to be able to
> > >close blocks opened in perl mode, or v/v.
> >
> > Urk. I'd rather not do that. The language that opens a block closes it.
>
>
>A reasonable rule. you ARE the voice of sanity aren't you.
Yep. It's a rather bizarre turn of events. I figure it's some sort of
Karmic payback... :)
Anyway, what we might want to talk about is how we want to switch parsers
on a large scale. (As opposed to minilanguages like the regex stuff)
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
