Whoa!
catch(...)
is one of the worst things to write. Think of it this way. You're writing a device driver. You've got a catch(...) to handle everything. In the device driver, you somehow manage to access memory you shouldn't. Maybe you buffer overwrite, maybe you overread due to a bad format string, who knows? Now the catch(...) catches the AV. How the hell have you helped anyone? They should have AV'd but instead you keep running even though the driver is completely shot and unlikely to work properly from here on in.
__________________
"It's a long story," says I, and let him up.
|