From: Marius Vollmer <mvo@zagadka.ping.de>
Cc: guile-devel@gnu.org, guile-user@gnu.org, lord@morrowfield.regexps.com
Subject: Re: why asyncs were created
Date: 03 Sep 2002 01:42:43 +0200 [thread overview]
Message-ID: <87wuq4ez64.fsf@zagadka.ping.de> (raw)
In-Reply-To: <200209022255.PAA08110@morrowfield.regexps.com>
Tom Lord <lord@regexps.com> writes:
> Since there is talk of removing the async abstraction, [...]
As a clarification, I have in mind to keep the "async" name and the
"async" behavior, but an async does not need to continue to be an
opaque object; it could just be a normal procedure that is used in a
special way.
Instead of
(let ((a (make-async PROC)))
(mark-async a))
one could just do
(mark-async PROC)
with the same meaning.
(make-async would continue to be provided.)
--
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:[~2002-09-02 23:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-02 22:55 why asyncs were created Tom Lord
2002-09-02 23:42 ` Marius Vollmer [this message]
2002-09-03 0:05 ` Tom Lord
2002-09-02 23: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=87wuq4ez64.fsf@zagadka.ping.de \
--to=mvo@zagadka.ping.de \
--cc=guile-devel@gnu.org \
--cc=guile-user@gnu.org \
--cc=lord@morrowfield.regexps.com \
/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).