Re: Opens but Won't Write to file

open() and print() return a true value when they succeed. Either your open call isn't succeeding or your prints arent working (maybe you're running out of disk space?)

In either case, you should ALWAYS check that open() succeeds, and it's probably a good idea to check print() too:

open FH,">","whatever" or die "Can't open whatever: $!";
[download]

is the standard procedure.

"What should it profit a man, if he should win a flame war, yet lose his cool?"

Comment on Re: Opens but Won't Write to file Download Code

Replies are listed 'Best First'.
Re^2: Opens but Won't Write to file by Bloodnok (Vicar) on Oct 30, 2009 at 23:09 UTC
I commend your suggestions, wrt the testing of the success (or otherwise) of calls, to the house. I would, however, debate your suggestion that ...your open call isn't succeeding... since the OP 'sees' a new file on each run - ergo, it strikes me that, as other, for more learned monks, have already pointed out elsewhere on this thread, the OP is suffering from buffering. A user level that continues to overstate my experience :-))	[reply]
Re^3: Opens but Won't Write to file by Joost (Canon) on Oct 30, 2009 at 23:20 UTC
I'm not completely sure that a failed open() call cannot leave an entry in the file system. On the other hand, buffering is the most likely cause of this "failure" (I expected the OP to have read the file after killing the process, which would have resulted in output if buffering is the problem). "What should it profit a man, if he should win a flame war, yet lose his cool?"	[reply]