On 22 Oct 2009, at 4:54 am, John Cowan wrote:
I spotted one error: in a let loop, the loop identifier is not just callable in a "procedure-like" way. It's bound to an actual first-class procedure which can be exported from the loop and called at any time.
Y'know, if I'd thought about it, I'd have expected that to be the case - but I'd only ever thought of using the loop identifier within the static and dynamic scope of the loop, as my brain is still steeped in lingering traces of C. Mmmm, beautiful delicious Scheme; how I wish I was using you in my day job. ABS -- Alaric Snell-Pym Work: http://www.snell-systems.co.uk/ Play: http://www.snell-pym.org.uk/alaric/ Blog: http://www.snell-pym.org.uk/archives/author/alaric/ _______________________________________________ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
