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: Tue, 15 Dec 2009 18:19:21 -0600	[thread overview]
Message-ID: <3ae3aa420912151619v165e032agccd15552a2dbcbd5@mail.gmail.com> (raw)
In-Reply-To: <87pr6fzur1.fsf@gnu.org>

2009/12/15 Ludovic Courtès <ludo@gnu.org>:

> Changes since the 1.9.5 pre-release:

>  *** Simplify representation of primitive procedures
>
>  It used to be that there were something like 12 different typecodes
>  allocated to primitive procedures, each with its own calling convention.
>  Now there is only one, the gsubr. This may affect user code if you were
>  defining a procedure using scm_c_make_subr rather scm_c_make_gsubr. The
>  solution is to switch to use scm_c_make_gsubr. This solution works well
>  both with the old 1.8 and and with the current 1.9 branch.

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.

I've needed this on multiple occasions. Each time, I eventually found
reasonably elegant alternative solutions, but not before some fair amount
of cursing, agonizing, exploring, and general pain.  (each alternative solution
required several hundred lines of carefully documented code, because it
did non-obvious things to find the needed data.)

--linas




  reply	other threads:[~2009-12-16  0:19 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 [this message]
2009-12-16 16:07   ` Ludovic Courtès
2009-12-16 21:51     ` Linas Vepstas

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=3ae3aa420912151619v165e032agccd15552a2dbcbd5@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).