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: Mon, 20 Jul 2009 11:20:45 +0200 Message-ID: <87y6qju2vm.fsf@gnu.org> References: <49dd78620809151317i3421081ey3337d678477046ab@mail.gmail.com> <87ljxsv80p.fsf@gnu.org> <49dd78620809171232n745ac8ecgd2c3936989ce723b@mail.gmail.com> <87myi5g98g.fsf@gnu.org> <49dd78620809180217p21c36802me305270af14a6f95@mail.gmail.com> <87my7j8jr6.fsf@gnu.org> <873a99ftap.fsf@gnu.org> <87ljmxsgxp.fsf@gnu.org> <874otkbv5j.fsf@gnu.org> <87ws64a17i.fsf@arudy.ossau.uklinux.net> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1248081692 31878 80.91.229.12 (20 Jul 2009 09:21:32 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 20 Jul 2009 09:21:32 +0000 (UTC) To: guile-devel@gnu.org Original-X-From: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Mon Jul 20 11:21:25 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 1MSp3j-0008Mq-Nu for guile-devel@m.gmane.org; Mon, 20 Jul 2009 11:21:24 +0200 Original-Received: from localhost ([127.0.0.1]:51520 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MSp3i-0000uv-Do for guile-devel@m.gmane.org; Mon, 20 Jul 2009 05:21:22 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MSp3X-0000t1-HQ for guile-devel@gnu.org; Mon, 20 Jul 2009 05:21:11 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MSp3R-0000o4-Vf for guile-devel@gnu.org; Mon, 20 Jul 2009 05:21:10 -0400 Original-Received: from [199.232.76.173] (port=39333 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MSp3R-0000nO-Dr for guile-devel@gnu.org; Mon, 20 Jul 2009 05:21:05 -0400 Original-Received: from main.gmane.org ([80.91.229.2]:32852 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 1MSp3Q-0006Xj-FC for guile-devel@gnu.org; Mon, 20 Jul 2009 05:21:04 -0400 Original-Received: from list by ciao.gmane.org with local (Exim 4.43) id 1MSp3K-00005p-1Z for guile-devel@gnu.org; Mon, 20 Jul 2009 09:20:58 +0000 Original-Received: from laptop-147-210-128-170.labri.fr ([147.210.128.170]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 20 Jul 2009 09:20:58 +0000 Original-Received: from ludo by laptop-147-210-128-170.labri.fr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 20 Jul 2009 09:20:58 +0000 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 33 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: laptop-147-210-128-170.labri.fr X-URL: http://www.fdn.fr/~lcourtes/ X-Revolutionary-Date: 2 Thermidor 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:YbohTVGRpuH4hAnlpyiaVfXpb6w= 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:8895 Archived-At: Hi Neil, Neil Jerram writes: > ludo@gnu.org (Ludovic Courtès) writes: > >> Andy Wingo writes: [...] >>> Array_handle_release is a bad idea. >> >> Fair enough. > > FWIW, I agree (I think with both of you) that `we might need it in > future' is not a good argument, but that API compatibility is. OK. So we can proceed with the removal, leaving a no-op macro when SCM_ENABLE_DEPRECATED == 1. Andy, can you take care of this? :-) > I'm pretty sure it was about allowing C code to efficiently access and > modify uniform vector contents, but at the same time supporting > operations which might require the underlying storage to be > reallocated. > > The latter operations could include enlarging an existing vector, or > copy-on-write. But AFAICT we never implemented either of those ideas, > and the existing code never changes the underlying storage of a > vector. Thanks for the information. Ludo'.