On Tue, 2012-10-16 at 16:38 -0400, Mark H Weaver wrote: > l...@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 >