From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Neil Jerram" Newsgroups: gmane.lisp.guile.user Subject: Re: srfi-88 keyword / symbol ambiguity Date: Mon, 21 Jul 2008 13:18:25 +0100 Message-ID: <49dd78620807210518j64fdf7e4m6b3e935ffd9763c9@mail.gmail.com> References: <2bc5f8210807201335v3f2ceaf0lb250c35b54ff4727@mail.gmail.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1216642729 22047 80.91.229.12 (21 Jul 2008 12:18:49 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 21 Jul 2008 12:18:49 +0000 (UTC) Cc: Guile User To: "Julian Graham" Original-X-From: guile-user-bounces+guile-user=m.gmane.org@gnu.org Mon Jul 21 14:19:35 2008 Return-path: Envelope-to: guile-user@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1KKuMS-0000oI-OQ for guile-user@m.gmane.org; Mon, 21 Jul 2008 14:19:29 +0200 Original-Received: from localhost ([127.0.0.1]:44161 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KKuLZ-0007aD-An for guile-user@m.gmane.org; Mon, 21 Jul 2008 08:18:33 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KKuLU-0007Xc-KB for guile-user@gnu.org; Mon, 21 Jul 2008 08:18:28 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KKuLT-0007V0-51 for guile-user@gnu.org; Mon, 21 Jul 2008 08:18:27 -0400 Original-Received: from [199.232.76.173] (port=37244 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KKuLS-0007Ug-Te for guile-user@gnu.org; Mon, 21 Jul 2008 08:18:26 -0400 Original-Received: from py-out-1112.google.com ([64.233.166.177]:28812) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KKuLS-0002hH-N2 for guile-user@gnu.org; Mon, 21 Jul 2008 08:18:26 -0400 Original-Received: by py-out-1112.google.com with SMTP id p76so701150pyb.1 for ; Mon, 21 Jul 2008 05:18:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=w2YFf3vKzOoO//98wkjUHuvr1Re6lZa4bOV7xZlZagg=; b=KXDiwDs05kZ2NUnrh+G7Jah8obwnGT3MG/RG0PwzJurVM6s670AbZ9Nw6rWl4hby+D phPiSkuGkdDRLV8L8vPKwJio+Z+pZTs26O5KYCC32SKC16tCKzF4ZdHf+HwfaH8e7CEl IT72/uJzu6lqS8qzDmV73cFYKe1lOgzMvhcqw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=tMB2/gd7zhXsUztKG3v3T6SmqDAfdso1JvhHun5sA3fCI5fkIgVQHiPbJH6xeNy83x 80/XPorB+5rxC9ANDki0yjh7pq8l8Hx96NHtvi9KbStDPV5pnR48ksAL0jD6FXrDbK3n trwue6vJQ07TCFHP4VTIhb+CcwkUBZlrxgxnA= Original-Received: by 10.114.148.1 with SMTP id v1mr2638623wad.199.1216642705413; Mon, 21 Jul 2008 05:18:25 -0700 (PDT) Original-Received: by 10.114.197.8 with HTTP; Mon, 21 Jul 2008 05:18:25 -0700 (PDT) In-Reply-To: <2bc5f8210807201335v3f2ceaf0lb250c35b54ff4727@mail.gmail.com> Content-Disposition: inline X-detected-kernel: by monty-python.gnu.org: Linux 2.6 (newer, 2) X-BeenThere: guile-user@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General Guile related discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: guile-user-bounces+guile-user=m.gmane.org@gnu.org Errors-To: guile-user-bounces+guile-user=m.gmane.org@gnu.org Xref: news.gmane.org gmane.lisp.guile.user:6687 Archived-At: 2008/7/20 Julian Graham : > > This is particularly bad because it breaks a lot of code that calls > `use-modules' with the :prefix or :rename syntax -- from looking at some of > the core libraries, it seems like it's pretty common to use rename-prefixes > that end in a colon. So, for example, the ice-9 debugger modules don't work > after loading `(srfi srfi-88)'. If it helps you in the short term, please feel free to look at patching those modules so that they use a prefix that doesn't end with a colon. I think that should be compatible in API terms, because the prefixed names are only used internally within the using module. > I'm not sure yet what the fix would be -- maybe the reader should avoid > converting a token into a postfix-style keyword if it's obvious from the > read state that a symbol is desired (i.e., the quote character is prefixed), > but that probably doesn't cover all the possibilities. That sounds very tricky! As Ludovic said, I think read options need somehow to be less global - whether via Guile-Reader, or otherwise. Neil