Re: RFC 140 (v1) One Should Not Get Away With Ignoring System Call Errors

2000-08-24 Thread Chaim Frenkel
"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

Re: RFC 140 (v1) One Should Not Get Away With Ignoring System Call Errors

2000-08-24 Thread Jarkko Hietaniemi
On Thu, Aug 24, 2000 at 02:09:15PM -0400, Chaim Frenkel wrote: "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

Re: RFC 140 (v1) One Should Not Get Away With Ignoring System Call Errors

2000-08-24 Thread Chaim Frenkel
"JH" == Jarkko Hietaniemi [EMAIL PROTECTED] writes: But the drawback would be that the actual victim may not be the primal cause. sub foo { my $fh = open(); ... Lots more code ... return $fh; } $victim = foo; print $victim "I'm helpless"; JH Tough. Not a nice attitude. The

Re: RFC 140 (v1) One Should Not Get Away With Ignoring System Call Errors

2000-08-23 Thread Jarkko Hietaniemi
I believe Dan said that he wanted to make objects a lot faster in P6. I don't think we should be precluded from requesting Things That Make Sense (tm) just because the current implementation is sub-optimal in performance if nothing inherently prevents a better implementation. I don't