[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: landed r7rs support
From: |
Amirouche Boubekki |
Subject: |
Re: landed r7rs support |
Date: |
Fri, 27 Dec 2019 08:53:09 +0000 |
Le lun. 18 nov. 2019 à 12:43, Mikael Djurfeldt <address@hidden> a écrit :
>
> On Sun, Nov 17, 2019 at 3:45 PM Andy Wingo <address@hidden> wrote:
>>
>> Hey all :)
>>
>> The library syntax for R7RS is a subset of R6RS, so to use R7RS you just
>> (import (scheme base)) and off you go. As with R6RS also, there are
>> some small lexical incompatibilities regarding hex escapes; see "R7RS
>> Incompatibilities" in the manual. Also there is a --r7rs command-line
>> option.
I do not think the library syntax for R7RS is a _subset_ of R6RS. For
one, it rely
on `define-library` instead of `library`.
For anyone trying to write (and benchmark!) code across scheme implementations,
you will have some luck with -x options:
-x EXTENSION add EXTENSION to the front of the load extensions
You can call guile with:
guile -x .guille.scm ...
And use .guile.scm as an extension for guile specific files.
Also, in R6RS library form, the form `import` is not defined that is
you can not do:
(library (mylib)
(export myfunc)
(import (scheme base)) ...)
ref: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=38760
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Re: landed r7rs support,
Amirouche Boubekki <=