From: Neil Jerram <neil@ossau.uklinux.net>
Cc: guile-devel@gnu.org
Subject: Re: Names for the C frame stuff
Date: 10 Jan 2004 16:37:42 +0000 [thread overview]
Message-ID: <m3fzensqsp.fsf@laruns.ossau.uklinux.net> (raw)
In-Reply-To: <ljllojah3c.fsf@troy.dt.e-technik.uni-dortmund.de>
>>>>> "Marius" == Marius Vollmer <marius.vollmer@uni-dortmund.de> writes:
Marius> Hi,
Marius> so I'm pondering over how to name the functions that are associated
Marius> with the new 'frame' concept. I'm now mostly convinced to use these
Marius> ones:
Marius> scm_frame_begin - Begin a frame
Marius> scm_frame_end - End it
Marius> scm_frame_unwind - Register a unwind handler
Marius> scm_frame_rewind - a rewind handler
Marius> scm_frame_block_asyncs - Block the asyncs
Marius> scm_frame_unblock_asyncs - Unblock them
Marius> scm_frame_current_input_port
Marius> scm_frame_current_output_port
Marius> scm_frame_current_error_port
Marius> - Set the indicated port temporarily
Marius> scm_frame_fluid - Set a fluid temporarily
Marius> etc.
Sorry to take so long to get back ... I like the design of this API,
and I also share your concern about flipping the API too much. 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_*.)
Regards,
Neil
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2004-01-10 16:37 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 [this message]
2004-01-11 1:25 ` Marius Vollmer
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=m3fzensqsp.fsf@laruns.ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--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).