"JH" == Jarkko Hietaniemi [EMAIL PROTECTED] writes:
JH "The first operation done on the return value of open() shall be defined()
JH or you shall regret your pitiful existence."? (a flag on the scalar coming
JH from open that makes any other op than defined() to die and defined() clears
JH the
If something fails, you should care.
Maybe.
The 'strict' pragma (or whatever form it takes in perl6) should
include in its 'default set of strictness' a new subpragma, 'system'.
This subpragma has the following semantics:
Ok, I can live with a pragma. :-) However, I do think that "system"
On Wed, Aug 23, 2000 at 08:17:18AM -0600, Tom Christiansen wrote:
"The first operation done on the return value of open() shall be defined()
or you shall regret your pitiful existence."? (a flag on the scalar coming
from open that makes any other op than defined() to die and defined() clears
On Wed, Aug 23, 2000 at 04:32:43AM -, Perl6 RFC Librarian wrote:
=head1 TITLE
One Should Not Get Away With Ignoring System Call Errors
=head1 ABSTRACT
=head1 EXECUTIVE SUMMARY
If something fails, you should care.
=head1 DESCRIPTION
The 'strict' pragma (or whatever form it
Jarkko Hietaniemi wrote:
I don't think we should assume that we can't scratch our nose without
getting overly object-happy. For the particular aspect I'm driving at
there is no *need* for objects of any kind, no catch, no throw, no
structured exceptions: I want the program simply to _die_.
At 04:32 AM 8/23/00 +, Perl6 RFC Librarian wrote:
One Should Not Get Away With Ignoring System Call Errors
Mailing List: [EMAIL PROTECTED]
I think this should be perl6-language-errors
In the following 'system calls' mean anything not in the core language
calling an external service, be
Perl6 RFC Librarian wrote:
=head2 Cheating Is Still Possible
Not ignoring the return value is of course no guarantee of doing
anything useful with the return value:
$so_what++ unless defined fork();
But detecting whether 'something useful' is done is squarely in
the realm of
