From: Neil Jerram <neil@ossau.uklinux.net>
Cc: mvo@zagadka.ping.de, guile-devel@gnu.org
Subject: Re: Non-system asyncs
Date: 11 Oct 2002 22:36:55 +0100 [thread overview]
Message-ID: <m3ptug8xoo.fsf@laruns.ossau.uklinux.net> (raw)
In-Reply-To: 200210100805.BAA16328@morrowfield.regexps.com
>>>>> "Tom" == Tom Lord <lord@regexps.com> writes:
Tom> Asyncs (both "system" and "non-system") are a mechanism for
Tom> scheduling asychronously invoked computation that can not be
Tom> explained by the semantics of ordinary evaluation. [...]
Thanks for the great description - it might be nice to incorporate
some of this into Marius's improved async docs.
However... it only makes sense for _system_ asyncs!
It isn't true for non-system (aka "user") asyncs that "some function
is invoked whose invocation can't be explained by the source of the
procedure being run at the time", because non-system asyncs have to be
run explicitly by calling `run-asyncs'.
In particular --
Tom> But why does the kernel get to define the set of asyncs? Why
Tom> not also have "synthetic asyncs"? It's a way to say to the
Tom> implementation: "here's a computation that you should run as
Tom> soon as you can, regardless of whatever else is going on".
-- absolutely, but in current Guile these are still "system" asyncs,
even when the computation is user-specified: see `system-async-mark'.
Tom> One might do incremental display updating that way, for
Tom> example.
Excellent example, but still an application of "system" asyncs.
So, unless I'm still missing something, your excellent description
just reinforces my point that non-system asyncs are pointless.
(Just a thought - is it possible that the semantics of non-system
asyncs might have changed since you knew them closely?)
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-11 21:36 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
2002-10-10 8:05 ` Tom Lord
2002-10-11 21:36 ` Neil Jerram [this message]
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=m3ptug8xoo.fsf@laruns.ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=guile-devel@gnu.org \
--cc=mvo@zagadka.ping.de \
/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).