diff options
| author | Father Chrysostomos <sprout@cpan.org> | 2013-06-18 16:51:57 -0700 |
|---|---|---|
| committer | Father Chrysostomos <sprout@cpan.org> | 2013-07-25 23:47:59 -0700 |
| commit | c370bd2ea3bafeee0cf4a12391eb41c288c25e2c (patch) | |
| tree | ac2ed689dea2618ac50f1d312caafcb6bb59a353 /pad.c | |
| parent | 325e1816dc5cd0a76cbe852add810d33cb1a95fb (diff) | |
| download | perl-c370bd2ea3bafeee0cf4a12391eb41c288c25e2c.tar.gz | |
pad.c: Expand pad_push SVf_READONLY explanation
Diffstat (limited to 'pad.c')
| -rw-r--r-- | pad.c | 5 |
1 files changed, 4 insertions, 1 deletions
@@ -715,7 +715,10 @@ which will be set in the value SV for the allocated pad entry: SVf_READONLY constant shared between recursion levels C<SVf_READONLY> has been supported here only since perl 5.20. To work with -earlier versions as well, use C<SVf_READONLY|SVs_PADTMP>. +earlier versions as well, use C<SVf_READONLY|SVs_PADTMP>. C<SVf_READONLY> +does not cause the SV in the pad slot to be marked read-only, but simply +tells C<pad_alloc> that it I<will> be made read-only (by the caller), or at +least should be treated as such. I<optype> should be an opcode indicating the type of operation that the pad entry is to support. This doesn't affect operational semantics, |