I'm just guessing (never heard of "DzSoft Perl Editor"), but if this happens to be "line 8" of your test script:
open FILE, 'C:\Perl\Perl practice\test.txt' or die $!;
then the error report would have something to do with the "open" statement and the file name string that you're giving it.
If the perl interpreter (perl.exe) is in a directory that's covered by your PATH environment variable in a DOS shell, try stepping away from the DzSoft IDE for a bit, and use the shell. Go to the directory where your test perl script is kept, and do:
perl name_of_test_script
If it gives a similar error report, try using forward slashes "/" instead of backslashes "\" in the file name that you pass to "open()". (I did say I was guessing...) Then make sure that the "test.txt" file really does exist in that exact path.
Just out of curiosity, what do you get when you run this command in a DOS shell:
perl -V
For that matter, if you went to a directory that contains some longer file names (and names with spaces in them, etc),
what would you get if you try this command:
perl -e 'opendir(D,"."); print join($/,readdir(D)),$/'
Do all the complete file names show up (long, with spaces,etc)? How about when you run that one-liner from within the IDE?
One other point: don't even think about trying to do regex substitutions on HTML text data for the sake of "expanding" visible white-space. It'll give you a headache. Doing it without HTML::TokeParser would be utterly wrong. Doing it with HTML::TokeParser (and, say, adding in strategic spots) would just be misguided and unsatisfying (you'd see some results, but you'd rarely see results that look good). |