bug#10252: bugs in array-map!, array-for-each, others

2011-12-08 Thread Daniel Llorens
Hello, I've found some bugs in array-map! and array-for-each. Apparently the array parameters only get used for the required arguments. The rest get base=0 and inc=1, which causes errors when those don't apply. 1.8.8 works fine. I have a patch and it solves my problem, but it needs a review. I

bug#10246: R6RS library form broken?

2011-12-08 Thread Andy Wingo
On Thu 08 Dec 2011 00:00, Ian Price writes: > Tobias Brandt writes: > >> (library (foo)) > > This is a misunderstanding on your part, I'm afraid. R6RS library forms > are intended to wrap the code[0]; they are not declarations to be placed at > the top. The manual does mention this[1], by noting

bug#10250: Problems using optargs with function docstrings

2011-12-08 Thread Peter TB Brett
There seems to be a nasty interference between the (ice-9 optargs) module, Guile's support for function docstrings, and a function's top-level definition context. For example, the following works: (use-modules (ice-9 optargs)) (define* (foo #:optional (bar "baz")) (define (frob p) (display p) (ne

bug#10250: Problems using optargs with function docstrings

2011-12-08 Thread Ian Price
Peter TB Brett writes: > (use-modules (ice-9 optargs)) > (define* (foo #:optional (bar "baz")) > "Docs go here" > (define (frob p) (display p) (newline)) > (frob bar)) > (foo) > > This generates an error: > > ERROR: In procedure memoization: > ERROR: Bad define placement (define (frob p) (display

bug#10250: Problems using optargs with function docstrings

2011-12-08 Thread Peter TB Brett
On Thu, 08 Dec 2011 23:39:22 +, Ian Price wrote: > Which version are you using? I'm on current stable-2.0(e7b2efd) This was with Guile 1.8.7 (guile-5:1.8.7-6.fc14). -- Peter Brett Remote Sensing Research Group Surrey Space Centre