Marco Antoniotti wrote: > > On Apr 22, 2005, at 10:02 AM, Bj�rn Lindberg wrote: > > >>>Great! I am curious, though, if a C++ library will work properly with >>>CMUCL. Are try/catch blocks working? How do global objects (if any) >>>get initialized? >>> >>> >> >>I (currently) do not have any global objects. As I said, the functions >>in the library available to CMUCL are declared as extern "C" to avoid >>the name mangling. Uncaught (on the C++ side) exceptions end up as a >>SIGABRT in CMUCL and drops me into the debugger. My intention is not to >>let any exceptions leak over though. Even if it is possible to recover >>from them in Lisp, you don't get any information from these errors. >> > > > I am no C++ expert, but I am curious. Are the SIGABRT a pretty common > way of passing exceptions out of C++ or is it something specific to > Solaris and the C++ compiler you used?
I am not sure to which extent it is specified, but every C++ compiler I can remember using would do this. I wouldn't describe it as "passing exceptions out of C++" as much as "terminating the program", though. Bj�rn
