Re: printf in if-statement

Nothing jumps out at me as being wrong in your code, but I do have some stylistic things and best practices you might want to consider...

You should really be checking the success of your open calls. Also, most people will suggest the three argument form of open and lexical file handles: open my $out, ">", "$resultsfile.corrected" or die "could not open $resultsfile.corrected: $!"
You don't need to use printf at all in this code. Using print and string interpolation is usually easier to read: print $out1 "$julday_old $day_cnt\n"
I think that if (! ($julday == $julday_old)) would be better written as if ($julday != $julday_old)

OK, enough of my opinions.

~~So the only real question I have is, are you sure that block of code is being reached? I assume you're seeing the printouts to the console, but I just thought I would ask.~~
Update: I reread the question and saw that the prints are showing up on stdout. I'm out of ideas...

Comment on Re: printf in if-statement Select or Download Code

Replies are listed 'Best First'.
Re^2: printf in if-statement by Utrecht (Novice) on Apr 21, 2009 at 14:21 UTC
Hi, thank you for your input. I am sorry I was bothering you, because I think I was a little too hasty with my question. For some reason, the print-statement is not executed realtime, but only after the while over filehandle INP is finished. I don't understand why this buffering occurs in this case as normally it doesn't, but the code works fine anyway.	[reply]
Re^3: printf in if-statement by almut (Canon) on Apr 21, 2009 at 14:49 UTC
I don't understand why this buffering occurs in this case as normally it doesn't I'd say it's the other way around: buffering is the default behaviour. Only under certain circumstances, the behaviour is changed, for example when the handle is connected to a terminal (like STDOUT, typically). In this case, line-buffering (as opposed to block-buffering) is used, because an interactive mode of operation is assumed. You could enable auto-flushing, though (on any handle): `use IO::Handle; open my $fh, ">", "test.out" or die $!; $fh->autoflush(); print $fh "..."; # is being written immediately` [download] (see also Re: Troubles with do...while loop and sleep (line- vs. block-buffered))	[reply] [d/l]