So this means I should be able to stop the dynwind from
plowing through any pure C++ function, in theory, right?
Yes.
(I'm still itching to upgrade the libguile API for C++,
if I only had the time to futz with it...)
IMHO this is possible only by wrapping libguile with
a C++ library.
David Fang wrote:
So this means I should be able to stop the dynwind from
plowing through any pure C++ function, in theory, right?
Yes.
(I'm still itching to upgrade the libguile API for C++,
if I only had the time to futz with it...)
IMHO this is possible only by wrapping libguile with
a
David Fang wrote:
C++ relies heavily on constructor-destructor duality
[...]
The implementation of guile's C-style exceptions using
setjmp/longjmp, however breaks this universal law.
[...]
In the event of scm_error_scm(), the destructors that
*should* be called in the frame of this
Hi all,
My initial use with guile (1.8 and 1.6) and C++ has been pretty
satisfactory so far -- I think scheme and C++ complement each other very
well, giving the best of both worlds. However, one serious problem
remains.
C++ relies heavily on constructor-destructor duality, namely
