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 heavy AI. As with all strictures, it may be lexically disabled: { no strict 'system'; # I know what I'm doing open STDERR, ">>log/$0"; # if ./log doesn't exist, don't open } # check syscalls again This is the stylistically correct way to ignore the return value of a system call. Jon -- Knowledge is that which remains when what is learned is forgotten. - Mr. King
- Re: RFC 140 (v1) One Should Not Get Away With Ignor... Jarkko Hietaniemi
- Re: RFC 140 (v1) One Should Not Get Away With I... Tom Christiansen
- Re: RFC 140 (v1) One Should Not Get Away Wi... Jarkko Hietaniemi
- Re: RFC 140 (v1) One Should Not Get Away With I... Tony Olekshy
- Re: RFC 140 (v1) One Should Not Get Away Wi... Peter Scott
- Re: RFC 140 (v1) One Should Not Get Awa... Jarkko Hietaniemi
- Re: RFC 140 (v1) One Should Not Ge... Tony Olekshy
- Re: RFC 140 (v1) One Should Not Get Away With I... Chaim Frenkel
- Re: RFC 140 (v1) One Should Not Get Away Wi... Jarkko Hietaniemi
- Re: RFC 140 (v1) One Should Not Get Awa... Chaim Frenkel
- Re: RFC 140 (v1) One Should Not Get Away With Ignoring S... Jon Ericson
- Re: RFC 140 (v1) One Should Not Get Away With Ignoring S... Michael G Schwern
- Re: RFC 140 (v1) One Should Not Get Away With Ignoring S... Nathan Wiger
- Re: RFC 140 (v1) One Should Not Get Away With Ignor... Nathan Torkington
- Re: RFC 140 (v1) One Should Not Get Away With I... Nathan Wiger