> The the way things are done in the current version of Chicken is wonky
> because the outline is like this:
>
>child = fork();
>if (!child) {
>// This code runs in the child process.
>execve(exefile, argv, envp);
>// Not only is the errno
Amir Teymuri wrote:
> I had a question about the objectives and reasons of allowing
> un-specified key arguments in functions as soon as i want to have some
> key arguments.
Any DSSSL style arguments (#!rest, #!optional and #!key) always are
optional arguments to the procedure.
You can think of
I had a question about the objectives and reasons of allowing
un-specified key arguments in functions as soon as i want to have some
key arguments. Take a look at the following case:
;;; The function
(define (foo a #!key b) (list a b))
Now passing any number of key arguments in addition to b
