Is it normal behaviour to get the '#unspecified' message.
; SLIME 2010-01-03
CSI (define (hello)
(display Hi))
#unspecified
CSI
___
Chicken-users mailing list
Chicken-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/chicken-users
Fixed upstream, including http://synthcode.com/scheme/match-cond-expand.scm,
which is basically suitable for Chicken modulo the module syntax.
Do we want the latest version for Chicken (with tree patterns and ..1),
or should I just patch this one bug?
--
Alex
On Tue, Jan 25, 2011 at 8:32 AM,
I'm only going to get more demanding out of what I'd like match to
do, I would like the latest version.
-Alan
On Thu, Jan 27, 2011 at 10:17:19PM +0900, Alex Shinn wrote:
Fixed upstream, including http://synthcode.com/scheme/match-cond-expand.scm,
which is basically suitable for Chicken modulo
I'm trying to use the matchable egg to detect #!key parameters in
functions I've constructed. I have functions that accept multiple
#!key parameters, and I'm not sure how to make the matchable egg
match |(func ... mykey: myvalue ...)|. That is, how to get the
matchable egg to match two
