Should we MAY a "curly-write" and "neoteric-write"? Or even "sweet-write"? David A. Wheeler 09 Apr 2013 21:56 UTC
Re: Should we MAY a "curly-write" and "neoteric-write"? Or even "sweet-write"? Mark H Weaver 09 Apr 2013 23:34 UTC
Re: Should we MAY a "curly-write" and "neoteric-write"? Or even "sweet-write"? David A. Wheeler 10 Apr 2013 00:14 UTC
Re: Should we MAY a "curly-write" and "neoteric-write"? Or even "sweet-write"? David A. Wheeler 10 Apr 2013 00:24 UTC
Re: Should we MAY a "curly-write" and "neoteric-write"? Or even "sweet-write"? David A. Wheeler 10 Apr 2013 04:11 UTC
Re: Should we MAY a "curly-write" and "neoteric-write"? Or even "sweet-write"? John Cowan 10 Apr 2013 01:56 UTC
Re: Should we MAY a "curly-write" and "neoteric-write"? Or even "sweet-write"? David A. Wheeler 10 Apr 2013 03:00 UTC
Re: Should we MAY a "curly-write" and "neoteric-write"? Or even "sweet-write"? John Cowan 10 Apr 2013 06:29 UTC
Re: Should we MAY a "curly-write" and "neoteric-write"? Or even "sweet-write"? David A. Wheeler 11 Apr 2013 02:26 UTC
Re: Should we MAY a "curly-write" and "neoteric-write"? Or even "sweet-write"? David A. Wheeler 11 Apr 2013 22:37 UTC
First cut at "curly-write" and "neoteric-write" with -shared and -cyclic versions David A. Wheeler 14 Apr 2013 22:29 UTC
Draft updated SRFI-110 and reference implementation David A. Wheeler 15 Apr 2013 04:09 UTC
Re: First cut at "curly-write" and "neoteric-write" with -shared and -cyclic versions beni.cherniavsky@xxxxxx 02 May 2013 08:00 UTC
Re: First cut at "curly-write" and "neoteric-write" with -shared and -cyclic versions David A. Wheeler 02 May 2013 22:46 UTC
Re: First cut at "curly-write" and "neoteric-write" with -shared and -cyclic versions David A. Wheeler 14 May 2013 00:47 UTC

Re: Should we MAY a "curly-write" and "neoteric-write"? Or even "sweet-write"? John Cowan 10 Apr 2013 01:56 UTC

David A. Wheeler scripsit:

> "Implementations <em>MAY</em> provide the procedures
> <var>curly-write</var>, <var>neoteric-write</var>, and/or <var>sweet-write</var>
> as writers that can write c-expressions, n-expressions, and t-expressions respectively.

I'd say forget sweet-write and go with curly-write and neoteric-write,
and go ahead and use MUST modals for them, without overspecifying
what they output.  R7RS systems MUST provide curly-write{simple,shared}
and neoteric-write-{simple,shared} as well.

As long as there is a good reference implementation, there is no reason
not to require these things.

--
Overhead, without any fuss, the stars were going out.
        --Arthur C. Clarke, "The Nine Billion Names of God"
                John Cowan <xxxxxx@ccil.org>