Since others have so competently answered your original question, I'll just pick on the rest. :)
### *Always* check the return when you open a file!
# open (FH3, ">lessons.txt");
open FH3, ">lessons.txt" or die "lessons.txt: $!\n";
print FH3 "Perl*Lesson1\n";
print FH3 "Perl*Lesson2\n";
print FH3 "Perl*Lesson3\n";
print FH3 "Java*Lesson1\n";
print FH3 "Java*Lesson2\n";
print FH3 "Java*Lesson3\n";
print FH3 "PHP*Lesson1\n";
print FH3 "PHP*Lesson2\n";
print FH3 "PHP*Lesson3\n";
### Lots of wasted typing, there. Doing it as a single line was OK - o
+r
### you could use a 'heredoc'.
print FH3 <<'Text_Block';
Perl*Lesson1
Perl*Lesson2
[etc...]
Text_Block
### Or you could even generate it - since it's all repetitive.
for my $lng (qw/Perl Java PHP/){ print "$lng*Lesson$_\n" for 1..3 };
--
Human history becomes more and more a race between education and catastrophe. -- HG Wells
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|