unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Linas Vepstas <linasvepstas@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guile-user@gnu.org, guile-devel@gnu.org
Subject: Re: GNU Guile 1.9.6 released (alpha)
Date: Wed, 16 Dec 2009 15:51:48 -0600	[thread overview]
Message-ID: <3ae3aa420912161351k52888e4fy2e032c39894ab673@mail.gmail.com> (raw)
In-Reply-To: <871viusy10.fsf@gnu.org>

2009/12/16 Ludovic Courtès <ludo@gnu.org>:
> Hi Linas,
>
> Linas Vepstas <linasvepstas@gmail.com> writes:
>
>> I have a new feature request -- it would be useful, in a variety of situations,
>> to be able to provide an opaque (void *) pointer when calling make_gsubr,
>> and then getting that pointer back again whenever the primitive is called.
>
> One solution is to use applicable smobs (‘scm_set_smob_apply ()’, 1.8+)
> or applicable structs (1.9).  How well does it work for you?

Someone (you?) suggested this earlier, on IRC. I explored but I could not
figure out how to use it -- I implemented something else.

TTN's suggestion of make-object-property appears to offer a simple
solution -- based on what I just now read in the guile manual.  Its not
obviously simpler than doing what I implemented .. maybe it is, the devil
is in the details (I have working code now, and have no desire to re-do it).

I just thought I'd bring this up since its been a recurring need for me,
and I figure others would have a similar need.

--linas




      reply	other threads:[~2009-12-16 21:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-15 23:24 GNU Guile 1.9.6 released (alpha) Ludovic Courtès
2009-12-16  0:19 ` Linas Vepstas
2009-12-16 16:07   ` Ludovic Courtès
2009-12-16 21:51     ` Linas Vepstas [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=3ae3aa420912161351k52888e4fy2e032c39894ab673@mail.gmail.com \
    --to=linasvepstas@gmail.com \
    --cc=guile-devel@gnu.org \
    --cc=guile-user@gnu.org \
    --cc=ludo@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).