>Are you saying that piped opens returning a "filehandle" object makes >testing for failure more troublesome? If so, I have an evil proposal >for you ... Let's make an "error" object (I hate to use that term) >that's *always* false but has some state we can get at. This thing would >encapsulate $!, $?, and friends. Modules (like DBI) could even add state, >but it would still be false. No, that's gross. A failed constructor should return undef. See my later message. --tom
- RFC: Modify open() and opendir() to return handles Nathan Wiger
- Re: Don't reply! RFC: Modify open() and opendir()... Nathan Wiger
- Re: RFC: Modify open() and opendir() to return ha... Bart Lateur
- Re: RFC: Modify open() and opendir() to retur... Tom Christiansen
- Re: RFC: Modify open() and opendir() to retur... Johan Vromans
- Re: RFC: Modify open() and opendir() to return ha... Tom Christiansen
- Re: RFC: Modify open() and opendir() to retur... Graham Barr
- Re: RFC: Modify open() and opendir() to r... Tom Christiansen
- Re: RFC: Modify open() and opendir() ... Jonathan Scott Duff
- Re: RFC: Modify open() and opend... Tom Christiansen
- Re: RFC: Modify open() and o... Graham Barr
- Re: RFC: Modify open() a... Tom Christiansen
- Re: RFC: Modify open() a... Graham Barr
- Re: RFC: Modify open() a... Tim Jenness
- Re: RFC: Modify open() a... Peter Scott
- Re: RFC: Modify open() a... Johan Vromans
- Re: RFC: Modify open() a... Steve Simmons
- try/catch (Was: Re: RFC:... Johan Vromans
- Re: try/catch (Was: Re: ... Hildo Biersma
- Re: try/catch (Was: Re: ... Johan Vromans