Most of the problems you've encountered regarding this project were well answered in the thread begun with your previous post, Problem printing contents of file.
So, please step back and review the responses previously provided - as a courtesy to PerlMonks... and for the wisdom you'll perhaps be able to absorb with somewhat more diligent effort.
By way of reminder of the information in some of those replies, note that when this code is checked (ie, perl -c scriptname) without "use strict; use warnings" the output is:
perl -c 693525.pl [Mon Jun 23 21:24:06 2008] 693525.pl: Unquoted string "step" may clash + with future reserved word at 693525.pl line 12. 693525.pl syntax OK
and with strict and warnings, this ensues:
~$ perl -c 693525.pl Content-type: text/html <h1>Software error:</h1> <pre>Bareword "step" not allowed while "strict subs&quo +t; in use at 693525.pl line 12. 693525.pl had compilation errors. </pre> <p> For help, please send mail to this site's webmaster, giving this error + message and the time and date of the error. </p> [Mon Jun 23 21:24:48 2008] 693525.pl: Bareword "step" not allowed whil +e "strict subs" in use at 693525.pl line 12. [Mon Jun 23 21:24:48 2008] 693525.pl: 693525.pl had compilation errors +.
Please consider adopting a personal policy of using strict and warnings until you are far more expert with perl... and -- if you absolutely must and know why you're doing so-- turn off the relevant strictures. Again, the previous thread offers several notes on this, the essence of which is that you should consider "strict" and "warnings" tools to help you write working code; not as some kind of punishment or penalty.
In reply to Re: why is the content of frame.txt file not displaying
by ww
in thread why is the content of frame.txt file not displaying
by ketaki
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |