From: Rob Browning <rlb@defaultvalue.org>
Cc: guile-devel@gnu.org
Subject: Re: Doing more with the new frames
Date: Tue, 13 Jan 2004 11:28:34 -0600 [thread overview]
Message-ID: <87wu7vahbx.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <87ad54tt9i.fsf@zagadka.ping.de> (Marius Vollmer's message of "Sun, 04 Jan 2004 02:08:41 +0100")
Marius Vollmer <mvo@zagadka.de> writes:
> This is quite nice I think, when you get the idea and use
> scm_block_async correctly. However, when people see scm_block_asyncs
> and scm_unblock_asyncs in async.h, they might be inclined to use them as
>
> scm_block_asyncs ();
>
> [ asyncs are blocked here? ]
>
> scm_unblock_asyncs ();
>
> This would be quite wrong. Ok, scm_block_asyncs is probably unique
> since there is also scm_unblock_asyncs which wouldn't be there for,
> say, scm_with_current_output.
>
> Should we worry?
As long as our documentation is good enough that people don't have to
figure things out by poking around in the headers and guessing, then I
suspect it's fine. It'd probably be a good idea to have cross-refs in
the scm_begin_frame docs to all the other relevant "modifier"
functions.
--
Rob Browning
rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2004-01-13 17:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-04 1:08 Doing more with the new frames Marius Vollmer
2004-01-13 17:28 ` Rob Browning [this message]
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=87wu7vahbx.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.org \
--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).