Re^5: Initial Devel::UncheckedOps, a macro for perl

Because not being able to write to STDOUT usually means that there is something more serious than a script error. Right? Or has my brain gone soft this week of vacation?

Comment on Re^5: Initial Devel::UncheckedOps, a macro for perl

Replies are listed 'Best First'.
Re^6: Initial Devel::UncheckedOps, a macro for perl by diotalevi (Canon) on Jun 19, 2004 at 12:11 UTC
I think you were thinking of throwing errors on STDOUT not being a valid handle. If someone had closed it before or something. This generalizes the error checking to any error including such favorites as ENOSPC. It'll still throw errors if the handle being written to isn't valid. Heck, this is how I did most of my testing - checking against a print to an invalid handle. It was too inconvenient to keep a full file system around just for testing. `print BAR "Hi!" or die $!; # Bad file descriptor at ...` [download]	[reply] [d/l]

Replies are listed 'Best First'.

Re^6: Initial Devel::UncheckedOps, a macro for perl
by diotalevi (Canon) on Jun 19, 2004 at 12:11 UTC

I think you were thinking of throwing errors on STDOUT not being a valid handle. If someone had closed it before or something. This generalizes the error checking to any error including such favorites as ENOSPC. It'll still throw errors if the handle being written to isn't valid. Heck, this is how I did most of my testing - checking against a print to an invalid handle. It was too inconvenient to keep a full file system around just for testing.

print BAR "Hi!" or die $!;
# Bad file descriptor at ...
[download]

[reply]
[d/l]