|
From: SourceForge.net <no...@so...> - 2005-01-26 16:46:39
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=2960702 By: johngaughan "don't you catch this way? catch (exception & e) to avoid slicing the class?" When catching exception objects you should always catch by reference. It won't hurt and it might help. My two cents: I am working on a C++ library that uses exceptions and I have no problems with catching DLL/SO exceptions in either MinGW/Win32 or GCC/Linux. This is what MinGW's GCC spits back at me: # g++ --version g++ (GCC) 3.4.2 (mingw-special) Isn't this the latest one, the same one included in the RC3 package? If so, this wouldn't be a compiler issue. I bet this is one of those dumb "forgot a semicolon" type of errors. Happens to me all the time :-) ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=286529 |