A passing test case

2008-01-25 Thread Gregory Marton
Hi folks, I just wanted to send in a test case for a bug that is fixed as of guile 1.8.2, but recently bit me, and it's just not that obvious to test for. It is essentially exposed in 1.8.1 by (let ((x 1/2)) (display x) (equal? x 1/2)) ===> #f ! Thanks for being so responsive to a

sending and and or as an argument links their behavior

2008-01-25 Thread Gregory Marton
Hi folks, I'm wondering what to make of this behavior, seen in both guile 1.8.1 and 1.8.3, discovered by my colleague L. Brown Westrick, cc:ed above: guile> (define (apply2 f a b) (f a b)) guile> (apply2 or #t #f) #t guile> (apply2 and #t #f) #t [ #f expected ] guile> (quit) [because we're d

comparing procedures

2008-01-25 Thread Gregory Marton
Hi folks, I'm trying to write a meaningful comparison operator for procedures. Clearly this wants more than procedure-source, because variables in the source may be bound to different values in the procedure-environment. I expected something like this to work: (define foo 3) (define bar (lamb

Re: Intel Mac-mini OSX 10.5.1 guile test results

2008-01-25 Thread Roger Mc Murtrie
On 25/01/2008, at 12:31 PM, Roger Mc Murtrie wrote: I'm having trouble implementing the patches. The problem seems to occur when autoconf runs. It generates configure with a CR after the 3 in the guile version number: #! /bin/sh # Guess values for system-dependent variables and create Makefi