diff options
| author | Jesse Vincent <jesse@bestpractical.com> | 2009-11-05 11:14:45 -0500 |
|---|---|---|
| committer | Jesse Vincent <jesse@bestpractical.com> | 2009-11-05 11:14:45 -0500 |
| commit | 88e1f1a2657a3a28cf3a7811902a09aca9e18986 (patch) | |
| tree | e7280ddd6c04915543c3850e403d06b8b5892524 /pod/perlsyn.pod | |
| parent | 9b583d5830e4b19cc53ab2180c0fd30418e764ed (diff) | |
| download | perl-88e1f1a2657a3a28cf3a7811902a09aca9e18986.tar.gz | |
Implement facility to plug in syntax triggered by keywords
Date: Tue, 27 Oct 2009 01:29:40 +0000
From: Zefram <zefram@fysh.org>
To: perl5-porters@perl.org
Subject: bareword sub lookups
Attached is a patch that changes how the tokeniser looks up subroutines,
when they're referenced by a bareword, for prototype and const-sub
purposes. Formerly, it has looked up bareword subs directly in the
package, which is contrary to the way the generated op tree looks up
the sub, via an rv2cv op. The patch makes the tokeniser generate the
rv2cv op earlier, and dig around in that.
The motivation for this is to allow modules to hook the rv2cv op
creation, to affect the name->subroutine lookup process. Currently,
such hooking affects op execution as intended, but everything goes wrong
with a bareword ref where the tokeniser looks at some unrelated CV,
or a blank space, in the package. With the patch in place, an rv2cv
hook correctly affects the tokeniser and therefore the prototype-based
aspects of parsing.
The patch also changes ck_subr (which applies the argument context and
checking parts of prototype behaviour) to handle subs referenced by an
RV const op inside the rv2cv, where formerly it would only handle a gv
op inside the rv2cv. This is to support the most likely kind of modified
rv2cv op.
[This commit includes the Makefile.PL for XS-APITest-KeywordRPN missing
from the original patch, as well as updates to perldiag.pod and a
MANIFEST sort]
Diffstat (limited to 'pod/perlsyn.pod')
| -rw-r--r-- | pod/perlsyn.pod | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/pod/perlsyn.pod b/pod/perlsyn.pod index 5e80901b09..d5fc4a72c1 100644 --- a/pod/perlsyn.pod +++ b/pod/perlsyn.pod @@ -272,6 +272,14 @@ conditional is about to be evaluated again. Thus it can be used to increment a loop variable, even when the loop has been continued via the C<next> statement. +Extension modules can also hook into the Perl parser to define new +kinds of compound statement. These are introduced by a keyword which +the extension recognises, and the syntax following the keyword is +defined entirely by the extension. If you are an implementor, see +L<perlapi/PL_keyword_plugin> for the mechanism. If you are using such +a module, see the module's documentation for details of the syntax that +it defines. + =head2 Loop Control X<loop control> X<loop, control> X<next> X<last> X<redo> X<continue> |