>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

Reply via email to