From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Andy Wingo Newsgroups: gmane.lisp.guile.devel Subject: Re: [PATCH] Add observation that ports are not thread-safe Date: Tue, 25 Mar 2014 20:39:09 +0100 Message-ID: <87vbv2qd9e.fsf@pobox.com> References: <1395746068-20604-1-git-send-email-dfsr@riseup.net> <87lhvys6ug.fsf@pobox.com> <874n2mb3vk.fsf@nebulosa.milkyway> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1395776361 2273 80.91.229.3 (25 Mar 2014 19:39:21 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 25 Mar 2014 19:39:21 +0000 (UTC) Cc: guile-devel@gnu.org To: "Diogo F. S. Ramos" Original-X-From: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Tue Mar 25 20:39:30 2014 Return-path: Envelope-to: guile-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1WSXC3-0002t9-NK for guile-devel@m.gmane.org; Tue, 25 Mar 2014 20:39:27 +0100 Original-Received: from localhost ([::1]:43902 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WSXC3-0006aZ-Cl for guile-devel@m.gmane.org; Tue, 25 Mar 2014 15:39:27 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:37873) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WSXBv-0006aE-Ut for guile-devel@gnu.org; Tue, 25 Mar 2014 15:39:24 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WSXBr-0004Qn-3h for guile-devel@gnu.org; Tue, 25 Mar 2014 15:39:19 -0400 Original-Received: from a-pb-sasl-quonix.pobox.com ([208.72.237.25]:36099 helo=sasl.smtp.pobox.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WSXBq-0004Qh-JT for guile-devel@gnu.org; Tue, 25 Mar 2014 15:39:15 -0400 Original-Received: from sasl.smtp.pobox.com (unknown [127.0.0.1]) by a-pb-sasl-quonix.pobox.com (Postfix) with ESMTP id 47E1510EAA; Tue, 25 Mar 2014 15:39:13 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=from:to:cc :subject:references:date:in-reply-to:message-id:mime-version :content-type; s=sasl; bh=UEybL/7cPO1BqbYnSPzerayjroA=; b=m9Uw9L Uh2i3NNiOVjcyH+w7GmQz3t9XMNqUq3GEfwQ1pnZxBDY29kqnMQf3hw+D9UaaK+D r1PGbr8Jh/CD6jY3pvuJ5NjRWj0L5W3Y7RQ8qAOHs91a5RltQayDhSS1DkO7aMZ6 /sItHhLg4ptQW6vDoh5bGZZ7DJItnJFkG6MYk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=from:to:cc :subject:references:date:in-reply-to:message-id:mime-version :content-type; q=dns; s=sasl; b=OmMeq710kexvL2b/cNjQwhVV6nuMMmih jA5rlNUQn0cwP7lM0VdomZQNP1aWW9NHLdS9lrHXmHXGeKxduEsB+f0DZyQs04NJ sEgb86sEsulO0KhlQ/9rbQS15fKe+tvjpFPbIp0jkPlXHgDxm3O0kQoVlYA5v/aU ju9myKoKXeA= Original-Received: from a-pb-sasl-quonix.pobox.com (unknown [127.0.0.1]) by a-pb-sasl-quonix.pobox.com (Postfix) with ESMTP id 3678610EA9; Tue, 25 Mar 2014 15:39:13 -0400 (EDT) Original-Received: from badger (unknown [88.160.190.192]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by a-pb-sasl-quonix.pobox.com (Postfix) with ESMTPSA id 8B17510EA6; Tue, 25 Mar 2014 15:39:12 -0400 (EDT) In-Reply-To: <874n2mb3vk.fsf@nebulosa.milkyway> (Diogo F. S. Ramos's message of "Tue, 25 Mar 2014 14:10:55 -0300") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) X-Pobox-Relay-ID: 246387AC-B455-11E3-861C-873F0E5B5709-02397024!a-pb-sasl-quonix.pobox.com X-detected-operating-system: by eggs.gnu.org: Solaris 10 X-Received-From: 208.72.237.25 X-BeenThere: guile-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Developers list for Guile, the GNU extensibility library" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Original-Sender: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.lisp.guile.devel:17011 Archived-At: On Tue 25 Mar 2014 18:10, "Diogo F. S. Ramos" writes: >> On Tue 25 Mar 2014 12:14, "Diogo F. S. Ramos" 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. Master is what will be 2.2. stable-2.0 is the 2.0.x series. Your point is well taken, that ports aren't threadsafe in 2.0; but it pains me to document a bug instead of fixing it ;-) > IMO the user should be informed about this limitation in stable, even if > it's going to go away. Sure. Would you mind posting a modified patch to this effect, noting that this situation is fixed in 2.2? Andy -- http://wingolog.org/