From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: ludo@gnu.org (Ludovic =?iso-8859-1?Q?Court=E8s?=) Newsgroups: gmane.lisp.guile.devel Subject: Re: array handles and non-local exits Date: Sun, 05 Jul 2009 13:14:05 +0200 Message-ID: <87my7j8jr6.fsf@gnu.org> References: <49dd78620809151317i3421081ey3337d678477046ab@mail.gmail.com> <87ljxsv80p.fsf@gnu.org> <49dd78620809171232n745ac8ecgd2c3936989ce723b@mail.gmail.com> <87myi5g98g.fsf@gnu.org> <49dd78620809180217p21c36802me305270af14a6f95@mail.gmail.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1246792564 28245 80.91.229.12 (5 Jul 2009 11:16:04 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 5 Jul 2009 11:16:04 +0000 (UTC) To: guile-devel@gnu.org Original-X-From: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Sun Jul 05 13:15:58 2009 Return-path: Envelope-to: guile-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1MNPgG-0006jT-P0 for guile-devel@m.gmane.org; Sun, 05 Jul 2009 13:14:49 +0200 Original-Received: from localhost ([127.0.0.1]:44554 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MNPgF-0007q4-Vn for guile-devel@m.gmane.org; Sun, 05 Jul 2009 07:14:48 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MNPg0-0007pE-Ff for guile-devel@gnu.org; Sun, 05 Jul 2009 07:14:32 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MNPfu-0007p2-QT for guile-devel@gnu.org; Sun, 05 Jul 2009 07:14:30 -0400 Original-Received: from [199.232.76.173] (port=48682 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MNPfu-0007oz-Gg for guile-devel@gnu.org; Sun, 05 Jul 2009 07:14:26 -0400 Original-Received: from main.gmane.org ([80.91.229.2]:50970 helo=ciao.gmane.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MNPfu-0003Li-5i for guile-devel@gnu.org; Sun, 05 Jul 2009 07:14:26 -0400 Original-Received: from list by ciao.gmane.org with local (Exim 4.43) id 1MNPfp-0005eC-KF for guile-devel@gnu.org; Sun, 05 Jul 2009 11:14:21 +0000 Original-Received: from reverse-83.fdn.fr ([80.67.176.83]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 05 Jul 2009 11:14:21 +0000 Original-Received: from ludo by reverse-83.fdn.fr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 05 Jul 2009 11:14:21 +0000 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 18 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: reverse-83.fdn.fr X-URL: http://www.fdn.fr/~lcourtes/ X-Revolutionary-Date: 17 Messidor an 217 de la =?iso-8859-1?Q?R=E9volution?= X-PGP-Key-ID: 0xEA52ECF4 X-PGP-Key: http://www.fdn.fr/~lcourtes/ludovic.asc X-PGP-Fingerprint: 821D 815D 902A 7EAB 5CEE D120 7FBA 3D4F EB1F 5364 X-OS: x86_64-unknown-linux-gnu User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.50 (gnu/linux) Cancel-Lock: sha1:VpgagVY7HdtoCIR5mO2law9Ht7E= X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6, seldom 2.4 (older, 4) X-BeenThere: guile-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Developers list for Guile, the GNU extensibility library" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Errors-To: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.lisp.guile.devel:8835 Archived-At: Hello, Andy Wingo writes: > I'm hacking on this code right now, and have come to think that > scm_array_handle_release is superfluous. It shouldn't protect against > concurrent modification of the data, as that should be done with > user-implemented mutexen. It obviously doesn't do anything now -- and > really, it doesn't have anything to do. I can't think of a /supported/ > modification of an array that will leave a pointer to the elements > invalid -- i.e. we have no truncation ops that I know of. How about copy-on-write stringbufs as produced by `substring'? I suppose it's only a problem is the stringbuf is accessed concurrently, though. Thanks, Ludo'.