From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: David Kastrup Newsgroups: gmane.lisp.guile.devel Subject: Re: Guile: What's wrong with this? Date: Wed, 04 Jan 2012 21:14:17 +0100 Organization: Organization?!? Message-ID: <87mxa3fco6.fsf@fencepost.gnu.org> References: <4F027F35.5020001@gmail.com> <1325603029.22166.YahooMailNeo@web37906.mail.mud.yahoo.com> <4F032C41.3070300@gmail.com> <877h17hjj2.fsf@netris.org> <1325687351.71432.YahooMailNeo@web37906.mail.mud.yahoo.com> <874nwbs9c4.fsf@pobox.com> <87ty4bfheq.fsf@netris.org> <87sjjvpav1.fsf@pobox.com> <87lipnfeqy.fsf@netris.org> <87fwfvp82u.fsf@pobox.com> <4F04B1A7.60003@gmail.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1325708081 23199 80.91.229.12 (4 Jan 2012 20:14:41 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Wed, 4 Jan 2012 20:14:41 +0000 (UTC) To: guile-devel@gnu.org Original-X-From: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Wed Jan 04 21:14:36 2012 Return-path: Envelope-to: guile-devel@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1RiXEK-0005gF-0j for guile-devel@m.gmane.org; Wed, 04 Jan 2012 21:14:36 +0100 Original-Received: from localhost ([::1]:43136 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RiXEJ-0007fr-AK for guile-devel@m.gmane.org; Wed, 04 Jan 2012 15:14:35 -0500 Original-Received: from eggs.gnu.org ([140.186.70.92]:49345) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RiXEG-0007fm-3L for guile-devel@gnu.org; Wed, 04 Jan 2012 15:14:32 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RiXEF-0001yt-74 for guile-devel@gnu.org; Wed, 04 Jan 2012 15:14:32 -0500 Original-Received: from lo.gmane.org ([80.91.229.12]:54451) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RiXEE-0001yp-Ug for guile-devel@gnu.org; Wed, 04 Jan 2012 15:14:31 -0500 Original-Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1RiXED-0005da-SH for guile-devel@gnu.org; Wed, 04 Jan 2012 21:14:29 +0100 Original-Received: from p508ec2ac.dip.t-dialin.net ([80.142.194.172]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 04 Jan 2012 21:14:29 +0100 Original-Received: from dak by p508ec2ac.dip.t-dialin.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 04 Jan 2012 21:14:29 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 19 Original-X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: p508ec2ac.dip.t-dialin.net X-Face: 2FEFf>]>q>2iw=B6, xrUubRI>pR&Ml9=ao@P@i)L:\urd*t9M~y1^:+Y]'C0~{mAl`oQuAl \!3KEIp?*w`|bL5qr,H)LFO6Q=qx~iH4DN; i"; /yuIsqbLLCh/!U#X[S~(5eZ41to5f%E@'ELIi$t^ Vc\LWP@J5p^rst0+('>Er0=^1{]M9!p?&:\z]|;&=NP3AhB!B_bi^]Pfkw User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.92 (gnu/linux) Cancel-Lock: sha1:ciMtuksR/xYkU7zXLAI2lBHL4/4= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-Received-From: 80.91.229.12 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:13293 Archived-At: Bruce Korb writes: > On 01/04/12 11:43, Andy Wingo wrote: >> The correct behavior is the status quo. We are considering adding a >> hack to produce different behavior for compatibility purposes. We don't >> have to worry about correctness in that case, only compatibility. IMO >> anyway :) > > It would be a nice added benefit if it worked as one would expect. > viz., you make actual, writable copies of strings you pull in so that > if the string-upcase function were to modify its input, then it > would not affect other SCMs with values that happen to be the same > sequence of bytes. If string-upcase modifies its input (or needs a mutable string to start with), this is a bug, in contrast to what string-upcase! may do. -- David Kastrup