From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: nalaginrut Newsgroups: gmane.lisp.guile.devel Subject: Re: [PATCH] Implement SRFI-105 curly infix expressions. Date: Thu, 18 Oct 2012 15:16:48 +0800 Organization: HFG Message-ID: <1350544608.2688.15.camel@Renee-SUSE.suse> References: <87hapxxvhv.fsf@tines.lan> <87y5j6xvbm.fsf@gnu.org> <87ipaatanh.fsf@tines.lan> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1350544630 26101 80.91.229.3 (18 Oct 2012 07:17:10 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 18 Oct 2012 07:17:10 +0000 (UTC) Cc: Ludovic =?ISO-8859-1?Q?Court=E8s?= , guile-devel@gnu.org To: Mark H Weaver Original-X-From: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Thu Oct 18 09:17:17 2012 Return-path: Envelope-to: guile-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1TOkM0-0000u9-5e for guile-devel@m.gmane.org; Thu, 18 Oct 2012 09:17:16 +0200 Original-Received: from localhost ([::1]:58886 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TOkLt-0004J1-0f for guile-devel@m.gmane.org; Thu, 18 Oct 2012 03:17:09 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:42079) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TOkLl-0004Fw-S9 for guile-devel@gnu.org; Thu, 18 Oct 2012 03:17:06 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TOkLh-0005GE-Du for guile-devel@gnu.org; Thu, 18 Oct 2012 03:17:01 -0400 Original-Received: from mail-vb0-f41.google.com ([209.85.212.41]:34670) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TOkLf-0005Fi-JT; Thu, 18 Oct 2012 03:16:55 -0400 Original-Received: by mail-vb0-f41.google.com with SMTP id v13so9664802vbk.0 for ; Thu, 18 Oct 2012 00:16:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:subject:from:to:cc:date:in-reply-to:references :organization:content-type:x-mailer:content-transfer-encoding :mime-version; bh=YW2XVO1mSn+7ec6+5Gw0Bd4cz4Rtol6ccX8tXib016k=; b=vcsB3oOOQfWaWjIfYgjFB9dhvAU4fNIHEjwkhQQz01t1+dCejhJlgwb3JWsjC6z7hi JWL0m1/lydntbJRselgDdWQPw8qOh6Cu72CKtMnf1Usbc0XhX4z4esbMM5cN2BuwAZ42 /3HdZCeTTZj3zem/0eziOyZR0xXKM0rDSjzF/qJqKaXv9KIsMELDFtBjRxGhaMwf0uqF mC7M/6tZqxrwc8SsPk6/rmqxZ0EcIVtlXtLHL2kxFO6dqah6Q7l9UjCdG4GmPfcAujyE UUFgG1EN7tHJBUTH/Rl5wmmywi83tNBGzfKcrgiBsx5jhao1cXGiu5avKTpstHvMmZWg BiTg== Original-Received: by 10.220.225.138 with SMTP id is10mr3848916vcb.24.1350544614821; Thu, 18 Oct 2012 00:16:54 -0700 (PDT) Original-Received: from [147.2.147.112] ([61.14.130.226]) by mx.google.com with ESMTPS id xf2sm1876947vec.12.2012.10.18.00.16.51 (version=SSLv3 cipher=OTHER); Thu, 18 Oct 2012 00:16:52 -0700 (PDT) In-Reply-To: <87ipaatanh.fsf@tines.lan> X-Mailer: Evolution 3.2.1 X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 209.85.212.41 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:14999 Archived-At: On Tue, 2012-10-16 at 16:38 -0400, Mark H Weaver wrote: > ludo@gnu.org (Ludovic Courtès) writes: > > My understanding was that the sweet-expressions folks already had > > something, no? > > The implementation they have (which they call a "demo") reimplements the > entire reader from scratch. There are several problems with this, the > worst of which is that it strongly discourages anyone from using the > syntax in code that they'd like to deploy. Yes, that's true! An integrated sweet-expression reader would be better. My modified implementation was a multi-language extension one. But now things has changed, sweet-expression became SRFI-105, so we ought to make it more seriously. > You can't simply publish a > module with '#!curly-infix' at the top and have people use it. You have > to ask them to install the sweet-expressions implementation first, and > then ask them to somehow arrange for your code to be read using the > special reader. > > > And there as also this preliminary patch: > > > > http://lists.gnu.org/archive/html/guile-devel/2012-03/msg00129.html > > > > What about applying first, then one above, then anything beyond? > > With respect to nalaginrut, that patch was only the beginning, and was > never turned into a full implementation. I have a fully-functional > patch that implements the full spec, complete with documentation, test > suite, and everything needed to enable people to easily use and deploy > curly-infix in their programs. > Well, I just noticed there's an item "make curly brace delimiter" on Mark's TODO list. And I did it at the volley. There's no SRFI-105 at that time, so I thought an easy implementation would be enough. > Mark >