unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Marius Vollmer <mvo@zagadka.ping.de>
Cc: guile-devel@gnu.org, guile-user@gnu.org
Subject: Re: why asyncs were created
Date: 03 Sep 2002 01:57:57 +0200	[thread overview]
Message-ID: <87heh8eygq.fsf@zagadka.ping.de> (raw)
In-Reply-To: <200209030005.RAA08472@morrowfield.regexps.com>

Tom Lord <lord@regexps.com> writes:

> 	> 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.
> 
> 
> Ah -- a representation issue, not a semantic issue?

Yep.

> What replaces the `got_it' flag in an async object?

Instead of setting a flag, you would cons the object onto a list of
objects that are considered marked.  At appropriate times, the list
would be checked to see whether it is non-empty.

Each thread would have such a list.

-- 
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


      reply	other threads:[~2002-09-02 23:57 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
2002-09-03  0:05   ` Tom Lord
2002-09-02 23:57     ` Marius Vollmer [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=87heh8eygq.fsf@zagadka.ping.de \
    --to=mvo@zagadka.ping.de \
    --cc=guile-devel@gnu.org \
    --cc=guile-user@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).