I am extremely pleased to announce that a draft version of R6RS is now available at www.r6rs.org . A copy will also be posted on schemers.org .
The charter provides for a six-month public comment period. Therefore the editors, in consultation with the steering committee, have provided a mechanism for comment and discussion. Details are also at www.r6rs.org .
The comment period is now open and will continue until March 15, 2007.
The steering committee thanks the editors for their intensive work on the draft R6RS, and looks forward to the public comment period.
"Mitchell Wand" <mwa...@gmail.com> writes: > I am extremely pleased to announce that a draft version of R6RS is now > available at www.r6rs.org . A copy will also be posted on > schemers.org .
In section 3.2.1 of draft 5.91, there is this definition:
However, <symbol escape> doesn't seem to be defined anywhere, and no such mechanism is described in section 3.2.3 either.
(Am I supposed to write "Section" with a capital S? There is both "cf. Section 3.3.1" and "see section 9.13".)
I am pleasantly surprised by the semicolon in the "\x123;" syntax.
> The charter provides for a six-month public comment period. Therefore > the editors, in consultation with the steering committee, have > provided a mechanism for comment and discussion. Details are also at > www.r6rs.org .
Apparently requires subscribing to a mailing list.
> I am pleasantly surprised by the semicolon in the "\x123;" syntax.
I'm a little annoyed by it actually. It's a semicolon but doesn't introduce a comment, so it introduces states and transitions that the lexer didn't actually need, and makes converting source back and forth between ASCII and Unicode require some parsing rather than just simple patternmatching.
I'm glad there's a terminator there. I just wish it wasn't a semicolon that doesn't introduce a comment. Even with the small complications of it being a semicolon that doesn't introduce a comment, it's better than the "different introductory characters signal different hex escape lengths at least one of which is utterly useless" meme that was first proposed.
Kalle Olavi Niemitalo wrote: >>The charter provides for a six-month public comment period. Therefore >>the editors, in consultation with the steering committee, have >>provided a mechanism for comment and discussion. Details are also at >>www.r6rs.org .
> Apparently requires subscribing to a mailing list.
If you like, you can set your preferences on the mailing list so as not to receive messages from it. The reason for requiring a subscribtion is purely pragmatic: formal comments that are accepted are forwarded to the mailing list, and to control spam and so on, the mailing list requires the originator of a message to be subscribed.
Mitchell Wand wrote: > I am extremely pleased to announce that a draft version of R6RS is now > available at www.r6rs.org . A copy will also be posted on > schemers.org .
In article <450a64a6$0$96151$742ec...@news.sonic.net>, Ray Dillinger <b...@sonic.net> wrote:
> Kalle Olavi Niemitalo wrote:
> > I am pleasantly surprised by the semicolon in the "\x123;" syntax.
> I'm a little annoyed by it actually. It's a semicolon but doesn't > introduce a comment, so it introduces states and transitions that > the lexer didn't actually need, and makes converting source back and > forth between ASCII and Unicode require some parsing rather than just > simple patternmatching.
> I'm glad there's a terminator there.
Why? It seems to be that whitespace makes an adequate terminator.
Ron Garret wrote: > In article <1158263178.510926.263...@i3g2000cwc.googlegroups.com>, > "Mitchell Wand" <mwa...@gmail.com> wrote:
> > I am extremely pleased to announce that a draft version of R6RS is now > > available at www.r6rs.org
> 133 pages. Oh my!
You looked at the contents page, the last page mentioned there is 133. But the document is 142 pages long.
I'm not sure that the simplicity of a language has much to do with the length of it's standard definition though. The standard definition is made to describe many things that are only of real interest to implementors, not to general users. Scheme is a simple language with a fairly simple standard, but it doesn't always seem to correlate strongly in that way.
Ron Garret <rNOSPA...@flownet.com> writes: >> > I am pleasantly surprised by the semicolon in the "\x123;" syntax.
>> I'm a little annoyed by it actually. It's a semicolon but doesn't >> introduce a comment, so it introduces states and transitions that >> the lexer didn't actually need, and makes converting source back and >> forth between ASCII and Unicode require some parsing rather than just >> simple patternmatching.
>> I'm glad there's a terminator there.
> Why? It seems to be that whitespace makes an adequate terminator.
This applies to string literals.
I'm also glad about this detail, and about the R6RS direction in general. The "\x123;" syntax with a semicolon happens to coincide with my language.
