From: Ilya Zakharevich <ilya@math.ohio-state.edu>
Date: Thu, 10 Oct 1996 02:30:38 +0000 (-0400)
Subject: perl 5.003_07: pod/perlvar.pod
X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=2c19844b698b17b45488d6c855e43f78c774c1f1;p=p5sagit%2Fp5-mst-13.2.git

perl 5.003_07: pod/perlvar.pod

Date: Wed, 9 Oct 1996 22:30:38 -0400 (EDT)
From: Ilya Zakharevich <ilya@math.ohio-state.edu>

$^E under OS/2.
---

diff --git a/pod/perlvar.pod b/pod/perlvar.pod
index e9a902e..b0e2cf3 100644
--- a/pod/perlvar.pod
+++ b/pod/perlvar.pod
@@ -427,12 +427,16 @@ operator.  (Mnemonic: What just went bang?)
 =item $^E
 
 More specific information about the last system error than that
-provided by C<$!>, if available.  (If not, it's just C<$!> again.)
-At the moment, this differs from C<$!> only under VMS, where it
-provides the VMS status value from the last system error.  The
+provided by C<$!>, if available.  (If not, it's just C<$!> again, except under
+OS/2.)
+At the moment, this differs from C<$!> only under VMS and OS/2, where it
+provides the VMS status value from the last system error, and OS/2 error
+code of the last call to OS/2 API which was not directed via CRT.  The
 caveats mentioned in the description of C<$!> apply here, too.
 (Mnemonic: Extra error explanation.)
 
+Note that under OS/2 C<$!> and C<$^E> do not track each other, so if an
+OS/2-specific call is performed, you may need to check both.
 
 =item $EVAL_ERROR