Marko Rauhamaa <ma...@pacujo.net> writes: > What you're saying points out a secondary problem that applies to > Guile C programming. If you have stored Guile smob references in, say, > third-party library objects, you'll need to carefully protect and > unprotect them.
It may be worth mentioning that this includes _all_ C++ STL container classes (like std::vector). If you want to employ them in connection with Guile2's automatic memory scanning, you need to use them with custom allocators. -- David Kastrup
