Re^2: Ulimit being reached

[viffer]

The ulimit is set at system level - and has since been increased. I wanted to trap an error when perl tried to write to a file and exceeded the ulimit. The closing file handle worked ok.

Since then we have come up with the following to trap the error - although it has thrown up a strange error of not liking the "|| die" appearing on a separate line.

#!/usr/local/bin/perl
use strict;
use warnings FATAL => 'all';

open(OUT, '>', "splat")
    or die "Opening (write) 'splat' $!";

while (1) {
        my $line = time().’’;

        # THIS WORKS
        print (OUT $line) || die "writing 'splat' $!";

       # But putting || die on another line does not. i.e:
       # print (OUT $line) 
       #       || die "writing 'splat' $!";
}

close(OUT)
    or die "Closing 'splat' $!";

The error message produced is:

writing 'splat'

A file cannot be larger than the value set by ulimit. at u3.pl line 12.

[eyepopslikeamosquito]

You should always use low precedence or (in preference to ||) with the "or die" idiom. Also, you should normally avoid parens when calling print, so this is the recommended way to write it:

print OUT $line or die "writing 'splat' $!";

For a working example, see my reply below.

Update: further notice that lexical file handles (e.g. $fh in my reply below) are preferred to the old global file handles (e.g. OUT in your example code).

[eyepopslikeamosquito]

# THIS WORKS
print (OUT $line) || die "writing 'splat' $!";

# But putting || die on another line does not. i.e:
# print (OUT $line) 
#       || die "writing 'splat' $!";

That's strange. They both work for me.

Moreover, I see no reason why they would be different, in fact Deparse tells me they produce identical code:

% cat id1.pl
 print (OUT $line) || die "writing 'splat' $!";

% perl -MO=Deparse id1.pl
die "writing 'splat' $!" unless print OUT $line;
id1.pl syntax OK

% cat id2.pl
 print (OUT $line)
    || die "writing 'splat' $!";

% perl -MO=Deparse id2.pl
die "writing 'splat' $!" unless print OUT $line;
id2.pl syntax OK

Though you could dig further into the root cause of the difference you experienced, I suggest you just stick to the low precedence or and avoid parens with print as described earlier.

[Discipulus]

...and if you need or want parens after print (not in the case you put the filehandle too, but in the case your list to be printed starts with something that need parens) to avoid the error print (...) interpreted as function at .. use the following trick:


       print +(43-1);

HtH
L*