[Chicken-users] Segfault srfi-34 (raise 'oops)

2012-03-14 Thread Mark Carter
I'm getting a segfault with srfi-34: $ csi CHICKEN (c)2008-2011 The Chicken Team (c)2000-2007 Felix L. Winkelmann Version 4.7.0.5-st linux-unix-gnu-x86 [ manyargs dload ptables ] compiled 2012-03-07 on miro (Linux) #;1 (use srfi-34) ; loading

Re: [Chicken-users] Segfault srfi-34 (raise 'oops)

2012-03-14 Thread Christian Kellermann
Hi Mark, * Mark Carter mcar...@markcarter.me.uk [120314 09:09]: I'm getting a segfault with srfi-34: $ csi CHICKEN (c)2008-2011 The Chicken Team (c)2000-2007 Felix L. Winkelmann Version 4.7.0.5-st linux-unix-gnu-x86 [ manyargs dload ptables ] compiled 2012-03-07 on miro (Linux)

[Chicken-users] amb egg bug/confusion

2012-03-14 Thread Alan Post
I'm confused by the following behavior in the amb egg: (require-extension extras amb) (pretty-print (amb-collect (amb 0 1 2))) (pretty-print (let ((s (amb 0 1 2))) (amb-collect s))) (exit) produces: (0 1 2) (0) I would expect both forms to produce (0 1 2). What am I missing? I'm

Re: [Chicken-users] amb egg bug/confusion

2012-03-14 Thread Thomas Chust
On Wed, 2012-03-14 at 18:23 -0600, Alan Post wrote: [...] (pretty-print (let ((s (amb 0 1 2))) (amb-collect s))) [...] produces: [...] (0) [...] Hello, to me this behaviour looks correct. amb-collect is supposed to collect all the different values its argument can take on, but in your

Re: [Chicken-users] amb egg bug/confusion

2012-03-14 Thread John Cowan
Alan Post scripsit: (pretty-print (let ((s (amb 0 1 2))) (amb-collect s))) You're assuming that the result of amb is an amb object that you can bind to a variable, but that's not how amb works. It provides a non-linear flow of control in the evaluation of its arguments, but once it