Email list hosting service & mailing list manager

Are we done? Are other changes needed to maximize adoption? David A. Wheeler (16 Sep 2012 19:49 UTC)
Re: Are we done? Are other changes needed to maximize adoption? Shiro Kawai (16 Sep 2012 23:46 UTC)
Re: Are we done? Are other changes needed to maximize adoption? Alan Manuel Gloria (17 Sep 2012 00:25 UTC)
Re: Are we done? Are other changes needed to maximize adoption? David A. Wheeler (17 Sep 2012 00:52 UTC)
Re: Are we done? Are other changes needed to maximize adoption? David A. Wheeler (17 Sep 2012 01:17 UTC)
Re: Are we done? Are other changes needed to maximize adoption? David A. Wheeler (17 Sep 2012 00:30 UTC)
Re: Are we done? Are other changes needed to maximize adoption? David A. Wheeler (17 Sep 2012 01:32 UTC)
Re: Are we done? Are other changes needed to maximize adoption? Alan Manuel Gloria (19 Sep 2012 01:35 UTC)
Re: Are we done? Are other changes needed to maximize adoption? David A. Wheeler (18 Sep 2012 02:45 UTC)

Re: Are we done? Are other changes needed to maximize adoption? Shiro Kawai 16 Sep 2012 23:45 UTC

I skimmed the revised spec, didn't see obvious problems.  I haven't
had a chance to actually implement and try it in Gauche yet, but
I hope soon I can.

The only comment so far is that the rather lengthy rational section;
I understand you have lots to say and they're all useful, but
the first time readers may wonder why you need so much rationals,
before she actually read the specification.  It occurred to me that
it might help if examples are presented before rationals.
(But the reader can click the link to jump to the specfication anyways,
so the order may not be important so much...)

A general comment---I don't know if future lispers will use this
alternative notation a lot, but when I provide a capability
to extend applications written in Gauche, customers sometimes
asked more traditional notation than bare S-exprs, and I needed
to hack up some crude syntax every time.  I wished if
there were an off-the-shelf alternative syntax that maps nicely
to S-expr.  This srfi (plus sweet-expressions) may serve as a
good option.