From: Neil Jerram <neil@ossau.uklinux.net>
Cc: Guile Development <guile-devel@gnu.org>
Subject: Re: Non-system asyncs
Date: 10 Oct 2002 08:03:30 +0100 [thread overview]
Message-ID: <m38z16ai7x.fsf@laruns.ossau.uklinux.net> (raw)
In-Reply-To: <873crftmjr.fsf@zagadka.ping.de>
>>>>> "Marius" == Marius Vollmer <mvo@zagadka.ping.de> writes:
Marius> Neil Jerram <neil@ossau.uklinux.net> writes:
>> [...] But I still don't see
>> what the point of non-system asyncs is
Marius> I'd say they are somewhat different from hooks in that you
Marius> can decide 'dynamically' which procedures to call. [...]
Marius> Hmm, are they causing harm?
Kind of, in that I'd like to document them intelligently -- which
means explaining why as well as what and how -- and I currently can't
see how to do that.
Perhaps the key is that I don't understand what you mean by deciding
dynamically which procedures to call - can you explain again?
Regards,
Neil
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-10-10 7:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-09 19:03 Non-system asyncs Neil Jerram
2002-10-09 19:55 ` Marius Vollmer
2002-10-10 7:03 ` Neil Jerram [this message]
2002-10-10 8:05 ` Tom Lord
2002-10-11 21:36 ` Neil Jerram
2002-10-11 23:36 ` Tom Lord
2002-10-13 17:57 ` 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=m38z16ai7x.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).