netterfield at astro.utoronto.ca
Wed Mar 16 02:58:25 CET 2005
On Tuesday 15 March 2005 19:39, George Staikos wrote:
> On Tuesday 15 March 2005 19:24, Barth Netterfield wrote:
> > But I don't feel strongly enough to suggest that anyone do anything about
> > it....
> I'd still like to know how to see this. That's why the assert() is
The point itself is more or less irrelevant, as no-one knows how to trigger
it, but the general principle may be interesting: How should the code handle
'can't imagine how it could happen, and can't see how it would be useful'
cases like this
i) debugging code + death to see why it happened.
rational: mystries are bad. if it happens, its probably a bug
ii) defensive code keep it from dieing here.
rational: death is bad, and maybe the code can survive the 'odd event'.
I've done both from time to time. In this case, I like ii....
More information about the Kst