id est is i.e.

Message-ID: <20050727014238.GA2582@mccoy.peters.homeunix.org>

p4raw-id: //depot/perl@25229

diff --git a/pod/perlfunc.pod b/pod/perlfunc.pod
index ed7d9b1..c21ca0d 100644 (file)
--- a/pod/perlfunc.pod
+++ b/pod/perlfunc.pod
@@ -1181,7 +1181,7 @@ This is useful for propagating exceptions:
 If LIST is empty and C<$@> contains an object reference that has a
 C<PROPAGATE> method, that method will be called with additional file
 and line number parameters.  The return value replaces the value in
-C<$@>.  ie. as if C<< $@ = eval { $@->PROPAGATE(__FILE__, __LINE__) }; >>
+C<$@>.  i.e. as if C<< $@ = eval { $@->PROPAGATE(__FILE__, __LINE__) }; >>
 were called.
 
 If C<$@> is empty then the string C<"Died"> is used.
@@ -2995,7 +2995,7 @@ to the temporary file first.  You will need to seek() to do the
 reading.
 
 Since v5.8.0, perl has built using PerlIO by default.  Unless you've
-changed this (ie Configure -Uuseperlio), you can open file handles to
+changed this (i.e. Configure -Uuseperlio), you can open file handles to
 "in memory" files held in Perl scalars via:
 
     open($fh, '>', \$variable) || ..

diff --git a/pod/perlguts.pod b/pod/perlguts.pod
index 82910c0..65b3d81 100644 (file)
--- a/pod/perlguts.pod
+++ b/pod/perlguts.pod
@@ -2171,7 +2171,7 @@ This function is a part of the public API.
 
 =item p
 
-This function has a C<Perl_> prefix; ie, it is defined as C<Perl_av_fetch>
+This function has a C<Perl_> prefix; i.e. it is defined as C<Perl_av_fetch>
 
 =item d
 

diff --git a/pod/perlhack.pod b/pod/perlhack.pod
index 1a88b52..9dc1053 100644 (file)
--- a/pod/perlhack.pod
+++ b/pod/perlhack.pod
@@ -877,9 +877,9 @@ retrieves the return op from it, and returns it.
 
 =item Exception handing
 
-Perl's exception handing (ie C<die> etc) is built on top of the low-level
+Perl's exception handing (i.e. C<die> etc) is built on top of the low-level
 C<setjmp()>/C<longjmp()> C-library functions. These basically provide a
-way to capture the current PC and SP registers and later restore them; ie
+way to capture the current PC and SP registers and later restore them; i.e.
 a C<longjmp()> continues at the point in code where a previous C<setjmp()>
 was done, with anything further up on the C stack being lost. This is why
 code should always save values using C<SAVE_FOO> rather than in auto

diff --git a/pod/perlintern.pod b/pod/perlintern.pod
index 3baecb4..74006e5 100644 (file)
--- a/pod/perlintern.pod
+++ b/pod/perlintern.pod
@@ -28,7 +28,7 @@ C<CvWEAKOUTSIDE> flag in the child. This allows us to determine under what
 circumstances we should decrement the refcount of the parent when freeing
 the child.
 
-There is a further complication with non-closure anonymous subs (ie those
+There is a further complication with non-closure anonymous subs (i.e. those
 that do not refer to any lexicals outside that sub). In this case, the
 anonymous prototype is shared rather than being cloned. This has the
 consequence that the parent may be freed while there are still active
@@ -268,7 +268,7 @@ Found in file pad.h
 
 =item SAVECLEARSV      
 
-Clear the pointed to pad value on scope exit. (ie the runtime action of 'my')
+Clear the pointed to pad value on scope exit. (i.e. the runtime action of 'my')
 
        void    SAVECLEARSV     (SV **svp)