From: William Morgan <wmorgan@masanjin.net>
Subject: scm_make_gsubr question
Date: Sun, 19 Jan 2003 15:40:23 -0500 [thread overview]
Message-ID: <20030119204023.GA22802@masanjin.net> (raw)
Dear Guile developers,
Is there a way to specify, at the time you call scm_make_gsubr, a user
data parameter which is passed to the corresponding C function? This
would allow the same C function to be used for multiple Guile
procedures, behaving differently based on the user data parameter.
(This is a standard mechanism in C callback-style libraries, e.g. glib.)
If not, I would like to submit a patch...
--
William <wmorgan@masanjin.net>
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next reply other threads:[~2003-01-19 20:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-19 20:40 William Morgan [this message]
2003-01-19 23:55 ` scm_make_gsubr question Neil Jerram
2003-01-20 8:24 ` Rob Browning
2003-01-20 8:58 ` Marius Vollmer
2003-01-20 9:00 ` Mikael Djurfeldt
2003-01-20 19:07 ` William Morgan
2003-01-20 20:03 ` Mikael Djurfeldt
2003-02-02 22:55 ` Dale P. Smith
2003-01-21 15:04 ` Marius Vollmer
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=20030119204023.GA22802@masanjin.net \
--to=wmorgan@masanjin.net \
/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).