introduce $^U, a global bit to indicate whether system

[p5sagit/p5-mst-13.2.git] / pod / perlfilter.pod

diff --git a/pod/perlfilter.pod b/pod/perlfilter.pod
index f3ab788..d5fae92 100644 (file)
--- a/pod/perlfilter.pod
+++ b/pod/perlfilter.pod
@@ -19,12 +19,10 @@ you'll soon learn. But first, the basics.
 =head1 CONCEPTS
 
 Before the Perl interpreter can execute a Perl script, it must first
-read it from a file into memory for parsing and compilation. (Even
-scripts specified on the command line with the C<-e> option are stored in
-a temporary file for the parser to process.) If that script itself
-includes other scripts with a C<use> or C<require> statement, then each
-of those scripts will have to be read from their respective files as
-well.
+read it from a file into memory for parsing and compilation. If that
+script itself includes other scripts with a C<use> or C<require>
+statement, then each of those scripts will have to be read from their
+respective files as well.
 
 Now think of each logical connection between the Perl parser and an
 individual file as a I<source stream>. A source stream is created when
@@ -57,7 +55,7 @@ Every source stream is associated with only one file.
 
 A source filter is a special kind of Perl module that intercepts and
 modifies a source stream before it reaches the parser. A source filter
-changes the our diagram like this:
+changes our diagram like this:
 
     file ----> filter ----> parser
 
@@ -510,8 +508,7 @@ doesn't know Perl. It can be fooled quite easily:
     EOM
 
 Such things aside, you can see that a lot can be achieved with a modest
-amount of code. I<[Note that Tuomas' toy VRML parser on p. 17 had the
-same difficulty parsing VRML strings that look like comments. -Jon]>
+amount of code.
 
 =head1 CONCLUSION