Phillip J. Eby wrote:
> At 07:23 PM 5/13/2005 +1000, Nick Coghlan wrote:
>> Sorry about that (I was in a hurry this morning). It was here:
>> http://www.joelonsoftware.com/articles/Wrong.html
>
> "Wrong" is an excellent title for that article; it's completely
> wrongheaded about exceptions. :)
At 07:23 PM 5/13/2005 +1000, Nick Coghlan wrote:
>Guido van Rossum wrote:
> >>P.S. The points regarding non-local flow control in Joel Spolsky's
> latest Joel
> >>on Software article (especially the links at the end) may have had
> something to
> >>do with my change of heart. . .
> >
> >
> > I'm
Guido van Rossum wrote:
>>P.S. The points regarding non-local flow control in Joel Spolsky's latest Joel
>>on Software article (especially the links at the end) may have had something
>>to
>>do with my change of heart. . .
>
>
> I'm a big fan of Joel. Care to share the specific URL for the artic
Phillip J. Eby wrote:
> Really, the only use case for suppressing exceptions is to, well, suppress
> exceptions that are being logged, shown to the user, sent via email, or
> just plain ignored. Guido's point, I think, is that these use cases are
> rare enough (yet simple and similar enough) th
At 03:00 PM 5/12/2005 -0500, Ka-Ping Yee wrote:
>This is all so intricate i'm not sure if i got it right. Somebody
>let me know if this looks right or not. (In any case, i look forward
>to the day when i can rely on someone else to get it right, and they
>only have to write it once!)
It looks fi
Here's another use case to think about.
Example 2: Replacing a File.
Suppose we want to reliably replace a file. We require that either:
(a) The file is completely replaced with the new contents;
or (b) the filesystem is unchanged and a meaningful exception is thrown.
We'd like to be able
