On Tue, May 30, 2006 at 11:55:56AM +0200, R. Mattes wrote: > On Tue, 2006-05-30 at 11:22 +0200, Joris van der Hoeven wrote: > > Hi all, > > > > I noticed a strange problem with the memory allocation of smobs and > > I fail to understand whether I am doing something wrong or whether > > this is a bug in Guile. > > > > Consider the (C++) smob code attached below to this message. > > All memory allocations are done from within C++, so the free_mysmob > > function returns 0. Now consider the following session: > > Since you seem to test from the REPL: do you have value history enabled > by accident (something like "(use-modules (ice-9 history))" in your > guile init file)? Anything printed will be kept bound to $1, $2 ... $n.
No, the example comes from an interactive TeXmacs session without history. The problem seems to be due to a side-effect of display concerning the print state. It might be good to document this side-effect. Thanks, Joris _______________________________________________ Guile-user mailing list [email protected] http://lists.gnu.org/mailman/listinfo/guile-user
