From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Julian Graham Newsgroups: gmane.lisp.guile.devel Subject: Re: r6rs incompatibilities Date: Wed, 26 May 2010 09:02:25 -0400 Message-ID: References: <983244.37247.qm@web37906.mail.mud.yahoo.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 X-Trace: dough.gmane.org 1274879024 29025 80.91.229.12 (26 May 2010 13:03:44 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Wed, 26 May 2010 13:03:44 +0000 (UTC) Cc: guile-devel To: Andy Wingo Original-X-From: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Wed May 26 15:03:43 2010 connect(): No such file or directory 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.69) (envelope-from ) id 1OHGG4-000679-4U for guile-devel@m.gmane.org; Wed, 26 May 2010 15:02:52 +0200 Original-Received: from localhost ([127.0.0.1]:37509 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OHGG2-00026K-GN for guile-devel@m.gmane.org; Wed, 26 May 2010 09:02:50 -0400 Original-Received: from [140.186.70.92] (port=59276 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OHGFs-000227-L0 for guile-devel@gnu.org; Wed, 26 May 2010 09:02:45 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OHGFh-0006M7-Iu for guile-devel@gnu.org; Wed, 26 May 2010 09:02:40 -0400 Original-Received: from ey-out-1920.google.com ([74.125.78.145]:30299) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OHGFh-0006IS-Ed for guile-devel@gnu.org; Wed, 26 May 2010 09:02:29 -0400 Original-Received: by ey-out-1920.google.com with SMTP id 13so529873eye.34 for ; Wed, 26 May 2010 06:02:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=A9mz6Yya0or+fg4RBrht6TgWQwZDvnQeFWcyS8YH9P4=; b=WpgbSAEvo9O06Luoi3+8aZ29a2ODHtTOhqFZkTyANOMJmUZoIZWxtdIUDnufa4GeQM mxIq681hurk9prk91g27WwiqyGURR+TXnzA3ILIqi2UEWWeZW0FE/4xu7VVLT1QvcQkD LM0NoShK2jOQN9KuvcYP09MctmSV7syWZoM40= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=RH+ZGIKsVxD66+2Gy0MFoC4c7QvPXEvpBpo1dDVsDcHhj9NRp///qWp0eVn4gTW953 4Q8WGnKydJ8+M3ZAB6bxeL7PwuVnkk0AJllk0dSk3nm4ZnDhfZXWQ4XWZnogUwgNlzGI c63ty51w05XtEVz/5+oKsNGeLsCFUQ2ts5r0U= Original-Received: by 10.213.108.134 with SMTP id f6mr1271811ebp.58.1274878946046; Wed, 26 May 2010 06:02:26 -0700 (PDT) Original-Received: by 10.213.17.206 with HTTP; Wed, 26 May 2010 06:02:25 -0700 (PDT) In-Reply-To: X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 2) 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:10372 Archived-At: Hey Andy, >> We could make this more general, as the r7 committees are wont to do: if >> #! is followed by whitespace or /, then read as a block comment; >> otherwise read one token. In our case, we would read #!foo as #:foo. I >> don't think this change would affect anyone. What do you think? > > Note that there are a couple of other #! constructs being considered for > scheme 7, for example to control case folding. It seems more or less > sensible. Perhaps we should read these as directives, and not as datums > at all. > > There is also the possibility of introducing a reader option for this > behavior. Any chance we could go with my (admittedly sloppy) approach (or something equally as quick) in the short term, and then, as they say in the 'biz, "iterate?" The above sounds sweet, but it seems like it'd make more sense to tackle those things post-2.0. Regards, Julian