diff options
| author | Neil Bowers <neilb@neilb.org> | 2022-03-16 23:50:01 +0000 |
|---|---|---|
| committer | Paul Evans <leonerd@leonerd.org.uk> | 2022-04-20 11:38:21 +0100 |
| commit | 7c90a9467d090b303d2a2b8745b0fad04426d07b (patch) | |
| tree | 3299ce72fe77548e70918d473feddc58dfc5803c /pod/perlfunc.pod | |
| parent | 774c7748146e99348eefc95bc735a36a2626d090 (diff) | |
| download | perl-7c90a9467d090b303d2a2b8745b0fad04426d07b.tar.gz | |
Doc changes to reflect that perl might not support taint
The central doc change is in perlsec.pod. This not only explains
that you can build a perl that doesn't support taint,
but shows how you can check whether your perl supports taint or not.
The other doc changes are mainly to note that taint might not
be supported, and to refer the reader to perlsec for more details.
Diffstat (limited to 'pod/perlfunc.pod')
| -rw-r--r-- | pod/perlfunc.pod | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/pod/perlfunc.pod b/pod/perlfunc.pod index d9d11ad9b0..c2c0867cf5 100644 --- a/pod/perlfunc.pod +++ b/pod/perlfunc.pod @@ -3885,7 +3885,7 @@ See L<perlfork> for more details. If there is no I<LIST> of processes, no signal is sent, and the return value is 0. This form is sometimes used, however, because it causes -tainting checks to be run. But see +tainting checks to be run, if your perl support taint checks. But see L<perlsec/Laundering and Detecting Tainted Data>. Portability issues: L<perlport/kill>. |