Re: Are we done? Are other changes needed to maximize adoption? David A. Wheeler 17 Sep 2012 00:30 UTC

```Shiro Kawai:
> 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.

Okay.  Maybe a "why is this so long?" paragraph belongs early in the rationale.  (If you skip the rationale, then you don't care how long it is.)

>  It occurred to me that
> it might help if examples are presented before rationals.
> so the order may not be important so much...)

The order is specified by the SRFI template.  And yes, I think a lot of people will just jump to the spec, and that's fine.

How about adding this to the intro part of the rationale?  (the examples are a subset of the examples in the specification):

====

<p>A few examples of c-expressions and their mappings are:</p>
<ul>
<li><samp>{n&nbsp;&lt;=&nbsp;5}</samp> &#8658;
<samp>(&lt;=&nbsp;n&nbsp;5)</samp></li>
<li><samp>{a * {b + c}}</samp> &#8658; <samp>(* a (+ b c))</samp></li>
<li><samp>{x eqv? &#96;a}</samp> &#8658; <samp>(eqv? x &#96;a)</samp></li>
<li><samp>{-(a) / b}</samp> &#8658; <samp>(/ (- a) b)</samp></li>
<li><samp>{f(a b) + g(h)}</samp> &#8658; <samp>(+ (f a b) (g h))</samp></li>
<li><samp>{{a &gt; 0} and {b &gt;= 1}}</samp> &#8658;
<samp>(and (&gt; a 0) (&gt;= b 1))</samp></li>
<li>
<samp>{length(x)&nbsp;&gt;=&nbsp;6}</samp>
&#8658;
<samp>(&gt;=&nbsp;(length&nbsp;x)&nbsp;6)</samp>
</ul>

<p>
This SRFI rationale is unusually long, especially when you compare it to
the simplicity of its specification.
However, the notation described in this SRFI builds on the
lessons learned from the many previous infix mechanisms that have been
developed for Scheme and related Lisp-based languages.
The authors believe that it is important to document why various
decisions were made, in particular, to show why this approach is
an improvement over past approaches and more likely to gain wide acceptance.
</p>

====

> 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