From: Joris van der Hoeven <vdhoeven@texmacs.org>
Cc: guile-user@gnu.org
Subject: Re: Problem with smobs
Date: Tue, 30 May 2006 12:12:47 +0200 [thread overview]
Message-ID: <20060530101247.GC6177@barah.math.u-psud.fr> (raw)
In-Reply-To: <1148982956.15230.4.camel@hobbes.mh-freiburg.de>
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
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
prev parent reply other threads:[~2006-05-30 10:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-30 9:22 Problem with smobs Joris van der Hoeven
2006-05-30 9:53 ` Mikael Djurfeldt
2006-05-30 10:09 ` Joris van der Hoeven
2006-05-30 10:27 ` Mikael Djurfeldt
2006-05-30 18:26 ` Neil Jerram
2006-05-30 19:20 ` Joris van der Hoeven
2006-05-30 13:55 ` Ludovic Courtès
2006-05-30 9:55 ` R. Mattes
2006-05-30 10:12 ` Joris van der Hoeven [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060530101247.GC6177@barah.math.u-psud.fr \
--to=vdhoeven@texmacs.org \
--cc=guile-user@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).