On Sat, Jul 23, 2016 at 02:09:37PM -0000, Father Chrysostomos wrote: > Dave Mitchell wrote: > > I'm currently smoking this branch: > > > > smoke-me/davem/sub_argsB3 > > > > which if all goes well and there are no objections, I plan to then merge > > into blead. > > I am still planning to implement sub ($x,\@y,\%z). I was wonder > whether I would wait for your branch to merge. So I would say: Yes, > please, go ahead and merge it. > > My work on allowing backslashes may conflict with whatever > OP_SIGNATURE work you are planning to do next. That will not make > things too hard for you, will it? I think it would be awkward if we we were both working on sig code at the same time. Perhaps I should do the \@y work? Is this agreed upon syntax? It there a thread I can peruse for the details? I assume its just a case of the parser flagging an OP_ARGELEM (with OPf_REF perhaps), and then for pp_argelem to store SvRV(rhs) in the pad slot, while croaking if the RHS isn't of the right type? -- Hofstadter's Law: It always takes longer than you expect, even when you take into account Hofstadter's Law.Thread Previous | Thread Next