Re: RFC 140 (v1) One Should Not Get Away With Ignoring System Call Errors
[email protected] (Chaim Frenkel) 24 Aug 2000 14:09:15 -0400
| Newsgroups | perl.perl6.language.errors |
|---|---|
| Message-ID | <[email protected]> |
>>>>> "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 flag) Ala, taint? Except the variable is tainted with death? Hmm, this would make two types of undef. Actually, if a callee could death-taint a variable then the return death_tainted(42) would make the caller check his values on first use. 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"; <chaim> -- Chaim Frenkel Nonlinear Knowledge, Inc. [email protected] +1-718-236-0183