Gabriel Sechan wrote:
From: Stewart Stremler <[EMAIL PROTECTED]>
(1) They're not accepted as universal, so "best practices" results in a
set of macros to "portably handle exceptions". You don't use try, you
use a MACROPREFIX_TRY, and a MACROPREFIX_END_TRY, and all that stuff...
plus you have to keep track of nested try-catch blocks, and use custom
throw macros, and so forth. It makes the whole exception thing so
useless that you might as well not use it at all, which is, I suspect,
the point.
Umm, what the hell are you talking about? I have *never* seen any
such macros used in C++ code. I have never seen a macro to do try,
throw, or carch ever. And while you can do nested try/catch blocks,
you don't need to do anything special for them. I have no clue where
you're coming from here.
Look at implementations of the STL, particularly older ones like GNU's
libstdc++ that came with gcc-2.95. It's there. It's awful.
--Chris
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-lpsg
