Hi Alex,
Alex Shinn skribis:
> 2012/2/26 Ludovic Courtès :
>> Hi,
>>
>> Alex Shinn skribis:
>>
>>> On Thu, Feb 23, 2012 at 7:06 AM, Andy Wingo wrote:
>>
>> [...]
>>
> * R7RS exceptions
Are they like R6RS exceptions?
>>>
>>> Yes, just the exceptions with no condition hierarchy.
>>
2012/2/26 Ludovic Courtès :
> Hi,
>
> Alex Shinn skribis:
>
>> On Thu, Feb 23, 2012 at 7:06 AM, Andy Wingo wrote:
>
> [...]
>
* R7RS exceptions
>>>
>>> Are they like R6RS exceptions?
>>
>> Yes, just the exceptions with no condition hierarchy.
>
> Ouch, like SRFI-35--. I’d be curious to see
Hi,
Alex Shinn skribis:
> On Thu, Feb 23, 2012 at 7:06 AM, Andy Wingo wrote:
[...]
>>> * R7RS exceptions
>>
>> Are they like R6RS exceptions?
>
> Yes, just the exceptions with no condition hierarchy.
Ouch, like SRFI-35--. I’d be curious to see the rationale for yet
another record API, and o
On Thu, Feb 23, 2012 at 7:06 AM, Andy Wingo wrote:
>
>> * datum labels for circular and shared substructures
>
> Yes!
Note this is one thing a reference implementation will
be provided for.
>> * nan? and finite? now accept complex numbers
>> (should probably change inf? and infinite? as well)
Hi Mark!
Hope all is well. I'm behind as usual. Just an additional perspective
here.
On Thu 09 Feb 2012 06:09, Mark H Weaver writes:
> R7RS TODO
I think you probably agree, but we should be clear about it in any case:
the current drafts are not final. I look forward to R7RS being a report
t
Hi,
On Thu 16 Feb 2012 22:05, l...@gnu.org (Ludovic Courtès) writes:
> I’m actually arguing that these feature symbols are largely useless, for
> they cannot be rigorously specified and would almost certainly lead to
> misuses.
I very much agree. I think that the R7RS should specify no features
Hi,
Alex Shinn skribis:
> On Mon, Feb 13, 2012 at 8:50 PM, Ludovic Courtès wrote:
[...]
>> For GNU/Linux, one could imagine adding a ‘linux-gnu’ symbol, for
>> instance. Likewise for GNU/kFreeBSD.
>
> I'd like to hear feature recommendations, but you'd need specific
> examples of where such
On Mon, Feb 13, 2012 at 8:50 PM, Ludovic Courtès wrote:
> Alex Shinn skribis:
>> On Mon, Feb 13, 2012 at 8:46 AM, Ludovic Courtès wrote:
>>> Alex Shinn skribis:
>>>
There is no "gnu" feature proposed in R7RS,
>>>
>>> That would be for GNU, aka. GNU/Hurd.
>>
>> Wouldn't the feature be bette
Hi,
Alex Shinn skribis:
> On Mon, Feb 13, 2012 at 8:46 AM, Ludovic Courtès wrote:
>> Alex Shinn skribis:
>>
>>> On Sat, Feb 11, 2012 at 12:53 AM, Ludovic Courtès wrote:
> * R7RS feature identifiers: r7rs, exact-closed, ratios, exact-complex,
> ieee-float, full-unicode, windows
On 13 February 2012 10:57, Alex Shinn wrote:
> On Mon, Feb 13, 2012 at 8:46 AM, Ludovic Courtès wrote:
>> Alex Shinn skribis:
>>> There is no "gnu" feature proposed in R7RS,
>>
>> That would be for GNU, aka. GNU/Hurd.
>
> Wouldn't the feature be better named "hurd" then?
>
> How can a system be
On Mon, Feb 13, 2012 at 8:46 AM, Ludovic Courtès wrote:
> Hi Alex,
>
> Thanks for your feedback.
>
> Alex Shinn skribis:
>
>> On Sat, Feb 11, 2012 at 12:53 AM, Ludovic Courtès wrote:
>>>
* R7RS feature identifiers: r7rs, exact-closed, ratios, exact-complex,
ieee-float, full-unicode,
Hi Alex,
Thanks for your feedback.
Alex Shinn skribis:
> On Sat, Feb 11, 2012 at 12:53 AM, Ludovic Courtès wrote:
>>
>>> * R7RS feature identifiers: r7rs, exact-closed, ratios, exact-complex,
>>> ieee-float, full-unicode, windows, posix, unix, darwin, linux, bsd,
>>> freebsd, solaris, i386
On Sat, Feb 11, 2012 at 12:53 AM, Ludovic Courtès wrote:
>
>> * R7RS feature identifiers: r7rs, exact-closed, ratios, exact-complex,
>> ieee-float, full-unicode, windows, posix, unix, darwin, linux, bsd,
>> freebsd, solaris, i386, x86-64, ppc, sparc, jvm, clr, llvm, ilp32,
>> lp64, ilp64, bi
Hi Mark,
Mark H Weaver skribis:
> l...@gnu.org (Ludovic Courtès) writes:
>
>> Mark H Weaver skribis:
[...]
>>> * R7RS feature identifiers: r7rs, exact-closed, ratios, exact-complex,
>>> ieee-float, full-unicode, windows, posix, unix, darwin, linux, bsd,
>>> freebsd, solaris, i386, x86-64,
l...@gnu.org (Ludovic Courtès) writes:
> Mark H Weaver skribis:
>
>> * bytevectors in core R7RS
>
> What does it mean? That bindings are available by default?
Yes.
>> * R7RS feature identifiers: r7rs, exact-closed, ratios, exact-complex,
>> ieee-float, full-unicode, windows, posix, unix, dar
Hello,
Mark H Weaver skribis:
> * bytevectors in core R7RS
What does it mean? That bindings are available by default?
[...]
> * bytevector-copy! with 3 args
> * bytevector-copy-partial{,!}
[...]
> * R7RS binary ports and bytevector ports
>* {textual-binary}-port?
>* binary-port?
>
Hello all,
I skimmed through the R7RS (draft 5) looking for things we need to do to
claim full compliance. Here's the list I came up with.
Mark
R7RS TODO
=
* optional ellipsis specifier for syntax-rules et al
* syntax-error
* define-values
* let-values and let*-values (without load
17 matches
Mail list logo