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:20:04 +0100 Organization: Organization?!? Message-ID: <87ipkrfcej.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> <4F048CBB.9020903@gmail.com> <87k457z5mv.fsf@Kagami.home> <4F04A8AF.9020205@gmail.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1325708432 25688 80.91.229.12 (4 Jan 2012 20:20:32 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Wed, 4 Jan 2012 20:20:32 +0000 (UTC) To: guile-devel@gnu.org Original-X-From: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Wed Jan 04 21:20:26 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 1RiXJy-0008Dp-0r for guile-devel@m.gmane.org; Wed, 04 Jan 2012 21:20:26 +0100 Original-Received: from localhost ([::1]:36907 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RiXJx-0000Bz-6z for guile-devel@m.gmane.org; Wed, 04 Jan 2012 15:20:25 -0500 Original-Received: from eggs.gnu.org ([140.186.70.92]:57377) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RiXJu-0000Bu-17 for guile-devel@gnu.org; Wed, 04 Jan 2012 15:20:22 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RiXJs-0002xT-ER for guile-devel@gnu.org; Wed, 04 Jan 2012 15:20:21 -0500 Original-Received: from lo.gmane.org ([80.91.229.12]:42630) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RiXJs-0002xM-2M for guile-devel@gnu.org; Wed, 04 Jan 2012 15:20:20 -0500 Original-Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1RiXJp-0008An-Cb for guile-devel@gnu.org; Wed, 04 Jan 2012 21:20:17 +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:20:17 +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:20:17 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 37 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:l1xr/oASO9B/5WK2jI4zL46gtMA= 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:13294 Archived-At: Bruce Korb writes: > Who knows where I learned the idiom. I learned the minimal amount of > Guile needed for my purposes a dozen years ago. My actual problem > stems from this: > >> Backtrace: >> In ice-9/boot-9.scm: >> 170: 3 [catch #t # ...] >> In unknown file: >> ?: 2 [catch-closure] >> In ice-9/eval.scm: >> 420: 1 [eval # ()] >> In unknown file: >> ?: 0 [string-upcase ""] >> >> ERROR: In procedure string-upcase: >> ERROR: string is read-only: "" >> Scheme evaluation error. AutoGen ABEND-ing in template >> confmacs.tlib on line 209 >> Failing Guile command: = = = = = >> >> (set! tmp-text (get "act-text")) >> (set! TMP-text (string-upcase tmp-text)) > > What in heck is string-upcase doing trying to write to its input > string? This looks like it might be just a bug. Could be that string-upcase creates its own copy of the string incorrectly including the immutable bit and then tries changing the string. No reason to play helter-skelter with the language. Instead the bug should be fixed. -- David Kastrup