I disagree about printf() errors.
With normal file operations, what I said is true. It is almost impossible for a print or printf to "fail" once a local Hard Disk file handle is open. One way would be "File system full", but in that case, a fatal exception is thrown - the calling program won't see that.
I did make a mistake in interpreting the exact situation. I would have written: return sprintf "..." because I favor explicit return statements. | [reply] [d/l] |
#!/usr/bin/env perl
use warnings;
use strict;
my $file = $^O eq 'MSWin32' ? "P:\\foo" : '/tmp/foo/bar';
open my $fh, '>', $file or die "$file: $!";
my $data = "\0" x 2_000_000;
print "Writing ", length $data, " bytes to $file\n";
printf $fh "%s", $data or warn "printf: $!";
close $fh or warn "close: $!";
print "Still not fatal\n";
__END__
Windows:
Install https://www.ltr-data.se/opencode.html/#ImDisk
As Administrator:
> imdisk -a -t vm -m P: -s 1M -p "/fs:fat /q /y"
> perl write.pl
Writing 2000000 bytes to P:\foo
printf: No space left on device at write.pl line 9.
close: No space left on device at write.pl line 10.
Still not fatal
> imdisk -D -m P:
Linux:
$ mkdir -vp /tmp/foo
$ sudo mount -t tmpfs -o size=1M,uid=`id -u` tmpfs /tmp/foo
$ perl write.pl
Writing 2000000 bytes to /tmp/foo/bar
printf: No space left on device at write.pl line 9.
close: No space left on device at write.pl line 10.
Still not fatal
$ sudo umount /tmp/foo
| [reply] [d/l] |
| [reply] |
| [reply] |