From: "Diogo F. S. Ramos" <dfsr@riseup.net>
To: Andy Wingo <wingo@pobox.com>
Cc: guile-devel@gnu.org
Subject: Re: [PATCH] Add observation that ports are not thread-safe
Date: Tue, 25 Mar 2014 14:10:55 -0300 [thread overview]
Message-ID: <874n2mb3vk.fsf@nebulosa.milkyway> (raw)
In-Reply-To: 87lhvys6ug.fsf@pobox.com
> On Tue 25 Mar 2014 12:14, "Diogo F. S. Ramos" <dfsr@riseup.net> writes:
>
>> It's not obvious that ports are not thread-safe and trying to have
>> multiple threads writing to one returns errors that are not
>> recognizable as been caused by this lack of thread-safeness.
>
> This is a bug, and it is fixed in master. FWIW.
oic
This is an interesting issue between master and stable.
Browsing through the history, I see master's commit
79657fd3ec264ecd533a62d349c2cf1a2be2df14, which I assume fixes this bug,
but this fix is not in the last stable version, released just some days
ago.
IMO the user should be informed about this limitation in stable, even if
it's going to go away.
next prev parent reply other threads:[~2014-03-25 17:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-25 11:14 [PATCH] Add observation that ports are not thread-safe Diogo F. S. Ramos
2014-03-25 14:14 ` Andy Wingo
2014-03-25 17:10 ` Diogo F. S. Ramos [this message]
2014-03-25 19:39 ` Andy Wingo
2014-03-25 20:36 ` Diogo F. S. Ramos
2014-04-15 11:24 ` Diogo F. S. Ramos
2014-03-26 5:10 ` Guile's I/O procedures should *not* do thread synchronization Mark H Weaver
2014-03-26 8:25 ` Andy Wingo
2014-03-26 15:32 ` Mark H Weaver
2014-03-26 19:45 ` Andy Wingo
2014-04-06 6:08 ` Mark H Weaver
2014-04-08 20:53 ` Ludovic Courtès
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=874n2mb3vk.fsf@nebulosa.milkyway \
--to=dfsr@riseup.net \
--cc=guile-devel@gnu.org \
--cc=wingo@pobox.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).