It seems to me that blackhole's match doesn't work:
$ bsc Loaded Black Hole. Gambit v4.6.0
(import (std misc/match)) (match 2 (2 #t) (_ #f))
*** ERROR -- Unbound variable: module#extract-syntactic-closure-list
I've also tried Alex Shinn's match:
(import lib/match) ; Alex Shinn's match (match 2 (2 #t) (_ #f))
#t
(match 'foo ('foo #t) (_ #f))
*** ERROR -- Unbound pattern variable quote
Maybe a bug with syntax-rules literals? I'm using the last master branch from github.
--marco
Afficher les réponses par date
21 apr 2010 kl. 14.55 skrev Marco Benelli:
It seems to me that blackhole's match doesn't work:
$ bsc Loaded Black Hole. Gambit v4.6.0
(import (std misc/match)) (match 2 (2 #t) (_ #f))
*** ERROR -- Unbound variable: module#extract-syntactic-closure-list
This was because of a bug in match, it used a function in Black Hole that has been removed. It is fixed now.
I've also tried Alex Shinn's match:
What is that?
/Per
From: Per Eckerdal per.eckerdal@gmail.com
This was because of a bug in match, it used a function in Black Hole that has been removed. It is fixed now.
Thank you very much.
I've also tried Alex Shinn's match:
What is that?
http://synthcode.com/scheme/match.scm
I've also some troubles with srfi-11 reference implementation:
Loaded Black Hole. Gambit v4.6.0
(import srfi-11)
(let-values (((a b) (values 0 1)) ((c d) (values 2 3))) (list a b c d))
=> (2 2 2 2) ;; should be (0 1 2 3)
(let*-values (((a b) (values 0 1)) ((c d) (values 2 3))) (list a b c d))
=> (0 0 2 2) ;; should be (0 1 2 3)
--marco
I've also some troubles with srfi-11 reference implementation:
Loaded Black Hole. Gambit v4.6.0
(import srfi-11)
(let-values (((a b) (values 0 1)) ((c d) (values 2 3))) (list a b c d))
=> (2 2 2 2) ;; should be (0 1 2 3)
(let*-values (((a b) (values 0 1)) ((c d) (values 2 3))) (list a b c d))
=> (0 0 2 2) ;; should be (0 1 2 3)
--marco
This issue is fixed now on github. Thanks for pointing it out.
Regards, Per
From: Per Eckerdal per.eckerdal@gmail.com
I've also some troubles with srfi-11 reference implementation: [...]
This issue is fixed now on github. Thanks for pointing it out.
Sorry for delay. Thank you very much.
--marco