On Wed, Feb 22, 2006 at 09:52:34PM -0500, Bob Rogers wrote:
Content-Description: message body text
>    The good news is that the attached patch makes this work.  The bad
> news is that it also breaks PGE, albeit in a small way.  Six of the
> "<after>" tests (mostly, but not exclusively, involving "<!after>") in
> t/compilers/pge/p6rules/builtins.t seem to go into an infinite loop.  I
> have been unable to figure this out, so I'm hoping it will be easy for
> someone who understands PGE.  (Maybe there's something in PGE that
> assumes that returning from a sub restores the state of the user stack?)

Surprisingly, the following rule infinite loops when applied to
a target string of "cb":

    <!after c>b

Perhaps equally surprisingly, neither the code generated for the
above rule nor the <after> subrule itself make use of either the 
"push" or "pop" opcodes.  

Still looking...

Pm

Reply via email to