From: Marius Vollmer <mvo@zagadka.de>
Cc: guile-devel@gnu.org
Subject: Re: Names for the C frame stuff
Date: Sun, 11 Jan 2004 02:25:04 +0100 [thread overview]
Message-ID: <87llofxonj.fsf@zagadka.ping.de> (raw)
In-Reply-To: <m3fzensqsp.fsf@laruns.ossau.uklinux.net> (Neil Jerram's message of "10 Jan 2004 16:37:42 +0000")
Neil Jerram <neil@ossau.uklinux.net> writes:
> In this case, it seems to me that we can usefully keep
> scm_c_call_with_blocked_asyncs etc. both for back compatibility and
> as examples of the use of the scm_frame_* API. (Assuming that the
> implementation of scm_c_call_with_blocked_asyncs can be exactly
> rewritten to use scm_frame_*.)
Yes, exactly. I don't see any reason to remove
scm_c_call_with_blocked_asyncs and other existing functions.
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2004-01-11 1:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-07 15:55 Names for the C frame stuff Marius Vollmer
2004-01-10 11:55 ` Dirk Herrmann
2004-01-11 0:19 ` Marius Vollmer
2004-01-10 16:37 ` Neil Jerram
2004-01-11 1:25 ` Marius Vollmer [this message]
2004-01-13 17:33 ` Rob Browning
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=87llofxonj.fsf@zagadka.ping.de \
--to=mvo@zagadka.de \
--cc=guile-devel@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).