> That's not how I see it. The filehandle is naturally true if it > succeeds. It's the undef value that wants to have more information. > In fact, you could view $! as a poor-man's way of extracting the error > that was attached to the last undef. If I were wealthy enough in time and patience to forego poor-man's error handling for exceptions and verbosity I'd be programming in C++ with PCRE. David T. Grove Blue Square Group [EMAIL PROTECTED] [EMAIL PROTECTED]
- Re: Properties and "0 but true". Austin Hastings
- Re: Properties and "0 but true". Jarkko Hietaniemi
- Re: Properties and "0 but true". Austin Hastings
- Re: Properties and "0 but true". Larry Wall
- Re: Properties and "0 but true". David Grove
- Re: Properties and "0 but true". Larry Wall
- RE: Properties and "0 but true". David Grove
- RE: Properties and "0 but true". Austin Hastings