Re: What would having a & prototype after the first position break?

Chris Nehren wrote:
> I'm fine with doing the work to add this feature. I would just like to
> be sure I don't break half of CPAN with my efforts.
> 
> Thoughts? Comments? Rallying praise? Rotten tomatoes?

I like the idea.  Implementing it may be complex, because the parser (perly.y) has a special branch of its listop rule for this case (search for LSTOPSUB).  To allow (&&), ($&), (&$&$), and all other variations would need infinite parser rules, if the current approach were to be used.  So that could never work.  Instead, the lexer (toke.c; search for PREBLOCK(LSTOPSUB)) would have to invent commas to feed to the parser.  You might need to add new possible values for PL_expect.  For an example of remembering what type of block we are in, see the last few commits on the sprout/overridesε branch, particularly ae8d0518822.

• Re: What would having a & prototype after the first position break? by Father Chrysostomos