Front page | perl.perl5.porters |
Postings from April 2012
On Sun Jan 15 12:51:08 2012, sprout wrote: > The keywords do, require and glob are currently not overridable as > keywords. Overrides cannot change their syntax, but only their > behaviour. In other words, overrides of these keywords are > actually callbacks, rather than overrides. > > I propose that whether overrides of those three keywords are actual > keyword overrides depend on whether the âoverridesâ feature is > enabled in the scope where the subroutine is defined, not where it > is used. This poses a slight problem in the default case (outside the scope of the overrides feature). If require is always a keyword (and it is, because the prototype cannot be overridden), then we have a keyword that behaves differently depending on whether there is a CORE:: prefix. So, which behaviour should \&CORE::require have? It should probably be the same as CORE::require. And requireâs fixed prototype should be treated as a special case. I was trying to come up with a model that would encompass all special cases, such that there wouldnât be any special cases any more (they all being CV-specific parsing rules), but I have failed in this particular case. Does anyone else (particularly Zefram, since a lot of this is based on his ideas) have ideas? -- Father Chrysostomos --- via perlbug: queue: perl5 status: open https://rt.perl.org:443/rt3/Ticket/Display.html?id=108286Thread Next