Re: IO::ALL (Was: check for errors on close())

2005-04-27 Thread Smylers
Sam Vilain writes: Smylers wrote: Sam (or any other IO::All users reading this), what's your experience of IO::All? How much effort has it saved you? Does it make your code look Hi Sam -- thanks for taking the time to answer. I've only just begun to reap the benefits of it. After

Re: IO::ALL (Was: check for errors on close())

2005-04-27 Thread Sam Vilain
Smylers wrote: I've only just begun to reap the benefits of it. After how long of using it? Does that mean that initially you found it more hassle? No, not at all. I've just only found myself using it twice so far. However, when I did I found it deliciously DWIMmy and extremely handy. eg, in

Re: IO::ALL (Was: check for errors on close())

2005-04-24 Thread Smylers
Sam Vilain writes: Eric Wilhelm wrote: Just spent way too much time trying to find a bug when it turns out that I just had a full disk. So, food for thought for today: close() does not always return true. close(FILE) or die file error: $!; You don't already check the return value

Re: IO::ALL (Was: check for errors on close())

2005-04-24 Thread A. Pagaltzis
* Smylers [EMAIL PROTECTED] [2005-04-24 13:55]: Sam (or any other IO::All users reading this), what's your experience of IO::All? How much effort has it saved you? Does it make your code look too confusing for other coders (I'm thinking of the overloaded comparison operators being used for