Sorry, but this is a pet peeve. The proper abbreviation for
"id est" is "i.e.", not "ie." or "ie". ARRRAGAGAFASD!
Sorry, I feel better now. Attached is a patch to fix the included
pod files.
Steve Peters
[EMAIL PROTECTED]
--- pod/perlfunc.pod.old 2005-07-26 20:21:51.000000000 -0500
+++ pod/perlfunc.pod 2005-07-26 20:22:25.000000000 -0500
@@ -1181,7 +1181,7 @@
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 { [EMAIL PROTECTED]>PROPAGATE(__FILE__,
__LINE__) }; >>
+C<$@>. i.e. as if C<< $@ = eval { [EMAIL PROTECTED]>PROPAGATE(__FILE__,
__LINE__) }; >>
were called.
If C<$@> is empty then the string C<"Died"> is used.
@@ -2995,7 +2995,7 @@
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) || ..
--- pod/perlguts.pod.old 2005-07-26 20:22:54.000000000 -0500
+++ pod/perlguts.pod 2005-07-26 20:23:39.000000000 -0500
@@ -2171,7 +2171,7 @@
=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
--- pod/perlhack.pod.old 2005-07-26 20:24:21.000000000 -0500
+++ pod/perlhack.pod 2005-07-26 20:25:03.000000000 -0500
@@ -877,9 +877,9 @@
=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
--- pod/perlintern.pod.old 2005-07-26 20:25:20.000000000 -0500
+++ pod/perlintern.pod 2005-07-26 20:26:03.000000000 -0500
@@ -28,7 +28,7 @@
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 @@
=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)
