summaryrefslogtreecommitdiff
path: root/pod/perlvar.pod
diff options
context:
space:
mode:
authorTony Cook <tony@develop-help.com>2020-08-27 12:21:47 +1000
committerKarl Williamson <khw@cpan.org>2020-08-27 14:51:04 -0600
commit8a65a5dce836b59980666a348d4740b2565f6121 (patch)
tree75c49e5f149e7a3eb9399b84549ebc80142d4b54 /pod/perlvar.pod
parente275abc06263fc695a06f3deb147e050a3bd1411 (diff)
downloadperl-8a65a5dce836b59980666a348d4740b2565f6121.tar.gz
not only system and library calls can set errno
Unfortunately I don't remember the ticket, but I remember one complaining that code like C<print $fh "..."> would set $! when $fh wasn't an open filehandle, so cover that case here too.
Diffstat (limited to 'pod/perlvar.pod')
-rw-r--r--pod/perlvar.pod3
1 files changed, 3 insertions, 0 deletions
diff --git a/pod/perlvar.pod b/pod/perlvar.pod
index 4812f0d9c6..0fd9e9aea8 100644
--- a/pod/perlvar.pod
+++ b/pod/perlvar.pod
@@ -1927,6 +1927,9 @@ It can be used immediately before invoking the C<die()> operator,
to set the exit value, or to inspect the system error string
corresponding to error I<n>, or to restore C<$!> to a meaningful state.
+Perl itself may set C<errno> to a non-zero on failure even if no
+system call is performed.
+
Mnemonic: What just went bang?
=item %OS_ERROR