Hello,
The R7RS-small spec does not seem to suggest a naming convention for
modules. It merely says that module name is a list of identifies. I take
that to mean that the following are equally valid:
(import (srfi/17))
(import (srfi 17))
(import (srfi schemers org 17))
(import (org schemers srfi
Among the 4 r7rs schemes I've been working with (chibi chicken gauche
sagittarius) there are various ways to refer to the srfis: (srfi-17)
(srfi :17) etc. At this point, they all support (srfi 17), so I've been
using that. I don't really care which form is standard, but I'm excited
about
Thanks.
It's good to see that some schemes are moving toward R7RS and that there is
a de-facto shared syntax emerging.
Cheers,
Daniel.
On 8 March 2014 17:35, Seth Alves al...@hungry.com wrote:
Among the 4 r7rs schemes I've been working with (chibi chicken gauche
sagittarius) there are
Hello everybody,
I was reading the documentation for mutate-procedure in the lolevel unit (
http://wiki.call-cc.org/man/3/Unit%20lolevel#mutate-procedure) but got
confused by the example given.
Should 'new' not be called 'old', or do I misunderstand?
Thx,
Pluijzer
Daniel Carrera scripsit:
The R7RS-small spec does not seem to suggest a naming convention for
modules. It merely says that module name is a list of identifies.
Identifiers and numbers, yes.
I take that to mean that the following are equally valid:
(import (srfi/17))
(import (srfi 17))
On Mar 8, 2014, at 10:12 AM, pluijzer . pluij...@gmail.com wrote:
Hello everybody,
I was reading the documentation for mutate-procedure in the lolevel unit
(http://wiki.call-cc.org/man/3/Unit%20lolevel#mutate-procedure) but got
confused by the example given.
Should 'new' not be called
After a quiet few months, I'm pleased to announce a new release of my
Coq au Vin blogware (available as a chicken egg). Release 0.3 does not
introduce any major new features; it is focused mainly on making a
more robust and secure product. I have made the following changes:
* Moved the FastCGI
Hello chickeners,
I am trying to wrap a function that accepts a function pointer with an
argument to a struct passed by value.
I don't know how to do this (and fear it is not possible) but maybe
somebody else has a solution.
A little example of what I mean:
#
typedef struct { int x, y; }
