Re: OT: C# vs. C++ (was Re: UNICODE conversion)
Maybe those people have huge screens where real estate is not a problem.
Those endless streams of try/catch/catch/catch can be annoying. Also, if
someone adds a new kind of exception and you don't know about it 'bam' you
get a call from your testing guys saying "your program crashed". I use
catch(...) at the end now and put something like "They did it again" in
there to let me know what's going on, but... :o)
Tom
"David Lowndes" <DavidL@example.invalid> wrote in message
news:5jiit391lltk2feu7d3is2chn5k6271110@4ax.com...
It seems the trend it going towards throwing exceptions even when
things go right just as a way of saying they went right (I.E., you got the
right kind of exception). That's a pet peeve of mine.
:)
It's a peeve of mine too.
I'd been fervently anti exceptions but hadn't realised until recently
why I was so against them when others seemed to think they're the best
thing since sliced bread.
I've come to the conclusion that the true believers in exceptions
probably use them correctly (at an overall application structure
level) whereas most real world code I've encountered uses them as a
goto. I kid you not - I've got loads of them in a project I've just
started working on :( There's tons of things like this:
int fn()
{
int retcode;
try
{
...
if (something fails)
throw;
}
catch ()
{
retcode = ...;
}
return retcode;
}
I see the code and weep.
Dave