diff options
| author | Zefram <zefram@fysh.org> | 2010-05-05 20:41:28 +0100 |
|---|---|---|
| committer | Jesse Vincent <jesse@bestpractical.com> | 2010-05-08 16:39:23 -0400 |
| commit | 5149cfce110f600477036b7ec146007b3c1a2ba8 (patch) | |
| tree | e7562f43c4dab9bda8a672a219833c875c74361e /pod | |
| parent | f8a182a2b55a40f05063407a8061c7140b1b5188 (diff) | |
| download | perl-5149cfce110f600477036b7ec146007b3c1a2ba8.tar.gz | |
perldelta item on PL_restartjmpenv
Diffstat (limited to 'pod')
| -rw-r--r-- | pod/perl5131delta.pod | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/pod/perl5131delta.pod b/pod/perl5131delta.pod index df47e4c48f..785edc3f69 100644 --- a/pod/perl5131delta.pod +++ b/pod/perl5131delta.pod @@ -244,6 +244,16 @@ XXX Changes which affect the interface available to C<XS> code go here. =item * +The protocol for unwinding the C stack at the last stage of a C<die> +has changed how it identifies the target stack frame. This now uses +a separate variable C<PL_restartjmpenv>, where previously it relied on +the C<blk_eval.cur_top_env> pointer in the C<eval> context frame that +has nominally just been discarded. This change means that code running +during various stages of Perl-level unwinding no longer needs to take +care to avoid destroying the ghost frame. + +=item * + XXX =back |