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.
Just like SH doesn't throw out all environment variables between
instructions.
SH is very much like this: you can have multiple parsers acting on
multiple HERE documents, one after the other, in case anyone wasn't
aware of that already, which I doubt.
