From: Andy Wingo <wingo@pobox.com>
To: Chaos Eternal <chaoseternal@shlug.org>
Cc: guile-user@gnu.org, guile-devel <guile-devel@gnu.org>
Subject: Re: un-determined behavior of asyncs
Date: Mon, 20 May 2013 20:37:05 +0200 [thread overview]
Message-ID: <878v39bir2.fsf@pobox.com> (raw)
In-Reply-To: <CAGyY8NsiZO-+u-Diryg_suWabXzcnOvJf0SrbpxxSCOLCs4Amg@mail.gmail.com> (Chaos Eternal's message of "Mon, 20 May 2013 22:44:26 +0800")
On Mon 20 May 2013 16:44, Chaos Eternal <chaoseternal@shlug.org> writes:
> I just want to understand whether this random execution order of
> asyncs is designed or desired or not-specified ?
Your program has no synchronization so I am not sure what you expect it
to do. There's not even any guarantee that the thread is running at
all, AFAICS.
You may have come upon a bug but I don't understand the test case very
well.
Andy
--
http://wingolog.org/
prev parent reply other threads:[~2013-05-20 18:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-20 14:44 un-determined behavior of asyncs Chaos Eternal
2013-05-20 18:37 ` Andy Wingo [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=878v39bir2.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=chaoseternal@shlug.org \
--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).