summaryrefslogtreecommitdiff
path: root/pod/perlfilter.pod
diff options
context:
space:
mode:
authorGurusamy Sarathy <gsar@cpan.org>2000-01-31 04:16:01 +0000
committerGurusamy Sarathy <gsar@cpan.org>2000-01-31 04:16:01 +0000
commit4449c45db36a9fb1a03b0fdb9e259facf9647898 (patch)
tree555b03874f0f399f13d3cd999b91ce5fdd5d11f8 /pod/perlfilter.pod
parent16070b82c8557c1a47b3ee4bee2b551efb7b3eb7 (diff)
downloadperl-4449c45db36a9fb1a03b0fdb9e259facf9647898.tar.gz
fix factual regression (-e doesn't create temporary files anymore)
p4raw-id: //depot/perl@4928
Diffstat (limited to 'pod/perlfilter.pod')
-rw-r--r--pod/perlfilter.pod10
1 files changed, 4 insertions, 6 deletions
diff --git a/pod/perlfilter.pod b/pod/perlfilter.pod
index a2eb1d855b..d5fae925b1 100644
--- 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