From: Panicz Maciej Godek <godek.maciek@gmail.com>
To: "guile-user@gnu.org" <guile-user@gnu.org>
Subject: Re: Threads and lexical scope
Date: Tue, 14 Jan 2014 15:28:59 +0100 [thread overview]
Message-ID: <CAMFYt2Zjz7R3AEbV5f2rmq1dTtSW61qOOt57wRWpHgTxDaVQZw@mail.gmail.com> (raw)
In-Reply-To: <CAMFYt2bNhmq93KZ+fsFMi2VQdvr-ervT_NrBZFAdY1MxBFr8dw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 286 bytes --]
2014/1/14 Panicz Maciej Godek <godek.maciek@gmail.com>
> Oh, I just realized that each thread was created in a new closure anyway,
> so they weren't able to share the variable. Sorry for the confusion.
>
It was a confusion, because the lexical scopes of threads are obviously
shared.
[-- Attachment #2: Type: text/html, Size: 669 bytes --]
prev parent reply other threads:[~2014-01-14 14:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-14 13:52 Threads and lexical scope Panicz Maciej Godek
2014-01-14 14:01 ` Panicz Maciej Godek
2014-01-14 14:10 ` Panicz Maciej Godek
2014-01-14 14:28 ` Panicz Maciej Godek [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=CAMFYt2Zjz7R3AEbV5f2rmq1dTtSW61qOOt57wRWpHgTxDaVQZw@mail.gmail.com \
--to=godek.maciek@gmail.com \
--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).