From: William Morgan <wmorgan@masanjin.net>
Subject: Re: scm_make_gsubr question
Date: Mon, 20 Jan 2003 14:07:08 -0500 [thread overview]
Message-ID: <20030120190707.GA29475@masanjin.net> (raw)
In-Reply-To: <xy7lm1gi4an.fsf@nada.kth.se>
Excerpts (reformatted) from Mikael Djurfeldt's mail of 20 Jan 2003 (EST):
> I don't think it's a good idea to add this to gsubrs.
My question is partially mitigated by your reply below, but I think it's
worth considering who your target audience is:
If it includes C programmers who want to link Guile in as a scripting
language, possibly who are not very fluent in Scheme, and possibly (as
was the case on guile-user recently) in addition to other scripting
languages, then this should be as easy as possible for them to do.
But if doing fairly reasonable (IMO) things like this requires
understanding tricky concepts and significant Guile-specific changes to
one's application, I think you risk alienating that class of users.
At any rate, I will defer to your (collective) judgement.
> We already have three different ways to do it:
>
> 1. applicable smobs
>
> 2. compiled closures (cclo)
>
> 3. entities and operators (applicable structs)
>
> Of these, 1 and 2 are easy to do from C.
This sounds promising. But I can't find any documentation on any of
these. In particular, can anyone point me to something for #1 or #2?
Thank you,
--
William <wmorgan@masanjin.net>
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-01-20 19:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-19 20:40 scm_make_gsubr question William Morgan
2003-01-19 23:55 ` 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 [this message]
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=20030120190707.GA29475@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).