Re: working with files

Without checking the return values of your open statements, can you be sure the files are actually being opened?

open( IN, '<', 'test.txt' ) or die "Couldn't open infile.\n$!";
open( OUT, '>', 'test.out' ) or die "Couldn't open outfile.\n$!";
[download]

You can also check to see that you're actually getting the results you want after the substitution by adding a print statement (for debugging purposes only) as follows:

# after your substitution...
print $_;
print OUT $_;
[download]

Dave

Comment on Re: working with files Select or Download Code

Replies are listed 'Best First'.
Re^2: working with files by texuser74 (Monk) on Nov 02, 2005 at 09:04 UTC
Dave, thanks for your reply `print $_;` [download] is not printing anything in the screen. the problem with my script is, program hangs as if an endless loop, no output to the screen or output file.	[reply] [d/l]
Re^3: working with files by davido (Cardinal) on Nov 02, 2005 at 09:14 UTC
This is a problem: `while(IN){` [download] It should be `while( <IN> ) {` [download] If you had been using warnings you would have seen this message: `Bareword found in conditional at yourscript.pl line xx. Name "main::IN" used only once: possible typo at yourscript.pl line xx +.` [download] And if you had been using strict, you would have seen this fatal message: `Bareword "IN" not allowed while "strict subs" in use at yourscript.pl +line xx. Execution of yourscript.pl aborted due to compilation errors.` [download] It will really help you to keep on top of these hard to spot bugs if you remember to start every script off with: `use strict; use warnings;` [download] Update: I believe someone already mentioned to you in an earlier thread that you should be using strictures and warnings. Strictures and warnings will cause Perl to complain when it encounters things that are probably bugs in your code (or at least bad practices). And all that noise is helpful in isolating and eliminating such bugs and bad practices. Dave	[reply] [d/l] [select]