R6RS Draft Available
Mitchell Wand
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.
Enjoy!
For the Steering Committee,
--Mitch Wand
Ron Garret
"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!
rg
Dragontamer
A lot of them are from the libraries.
--Dragontamer
Kalle Olavi Niemitalo
> 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:
<initial> --> <constituent> | <special initial>
| <symbol escape>
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.
Ray Dillinger
>
> 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.
Bear
Anton van Straaten
>>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.
Anton
ivant
> 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 .
Is there a summary of what has changed from R5RS?
--
Ivan
Anton van Straaten
See the status report from June 2006:
http://schemers.org/Documents/Standards/Charter/
It predates the new draft, but the overall picture is there.
Ron Garret
Ray Dillinger <be...@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.
rg
Rob Thorpe
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.
Marcin 'Qrczak' Kowalczyk
>> > 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.
--
__("< Marcin Kowalczyk
\__/ qrc...@knm.org.pl
^^ http://qrnik.knm.org.pl/~qrczak/
MJ Ray
> Kalle Olavi Niemitalo wrote:
> > 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.
Requiring all consultation responders to spend time subscribing
and configuring preferences is only pragmatic for those running the
consulation. It's shovelling costs on to consultation responders,
which isn't pragmatic if you're considering the whole community.
It would be less expensive globally (=more pragmatic for the community)
for one person to review non-subscriber responses, especially if combined
with more usual spam countermeasures. I expect we can find at least
one reviewer from this audience - if wanted, I will do it when I get
back online properly (expected late next week).
--
MJR/slef