- iterate-devel - mailman3.common-lisp.net

[iterate-devel] iterate shadows CL:COUNT (bug report)
by mandeep singh 03 Jul '07

03 Jul '07

For example: (iter (for i in '(1 2 3 4)) (for c = (count i (list 234 234 2))) (collect c)) fails because CL:COUNT is shadowed by iterate and so i cant call the function from that scope. A workaround is: (iter (for i in '(1 2 3 4)) (for c = (funcall #'cl:count i (list 234 234 2))) (collect c)) But it is not nice to use this work-around. regards, msingh.

1 0

[iterate-devel] Trouble using iterate (ASDF issues ?)
by Olivier Drolet 02 Jul '07

02 Jul '07

Greetings all, I can't seem to get iterate to work. After configuring my init file, and using the relevant ASDF commands, I've successfully installed, loaded, and used libraries like cl-ppcre, but iterate fails to work. My setup is Mac OS X 10.4.10 on PPC G5 running: - Aquamacs 1.0b (Emacs 22.1) - Slime 2.0 - SBCL 1.0.2 I read the [iterate-devel] list and found someone who had a similar problem: > -------------------------------------------------- > [iterate-devel] Problem with new iterate install > > Phil pbpublist at comcast.net > Sat Mar 18 16:17:42 EST 2006 > > Previous message: [iterate-devel] Count is a CL function > Next message: [iterate-devel] Problem with new iterate install > Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] > > > I am attempting to get iterate (1.4 from common-lisp.net page) going > and could use some help. I've followed the docs on common-lisp.net > and d/l'd the package and loaded with asdf but when I attempt > something simple like (iter (for i from 1 to 10) (collect i)) to > verify the installation, errors are received (undefined variable i) > which I'm interpreting as the iterate install has something wrong. > I'm having these problems both on Lispworks and OpenMCL. Any > pointers are appreciated... > -------------------------------------------------- Here's what I get when I try the same thing: > -------------------------------------------------- > CL-USER> (iter (for i from 1 to 10) (collect i)) > ; in: LAMBDA NIL > ; (COLLECT I) > ; > ; caught STYLE-WARNING: > ; undefined function: COLLECT > > ; (FOR I FROM 1 TO 10) > ; > ; caught STYLE-WARNING: > ; undefined function: FOR > ; > ; caught WARNING: > ; undefined variable: FROM > ; > ; caught WARNING: > ; undefined variable: I > > ; (ITER (FOR I FROM 1 TO 10) (COLLECT I)) > ; > ; caught STYLE-WARNING: > ; undefined function: ITER > > ; (FOR I FROM 1 TO 10) > ; > ; caught WARNING: > ; undefined variable: TO > > ; > ; caught WARNING: > ; These variables are undefined: > ; FROM I TO > > ; > ; caught STYLE-WARNING: > ; These functions are undefined: > ; COLLECT FOR ITER > ; > ; compilation unit finished > ; caught 4 WARNING conditions > ; caught 4 STYLE-WARNING conditions > -------------------------------------------------- And, to be exhaustive: > -------------------------------------------------- > Restarts: > 0: [ABORT-REQUEST] Abort handling SLIME request. > 1: [ABORT] Exit debugger, returning to top level. > > Backtrace: > 0: (SB-INT:SIMPLE-EVAL-IN-LEXENV I #<NULL-LEXENV>) > 1: (SB-INT:SIMPLE-EVAL-IN-LEXENV (FOR I FROM 1 TO 10) #<NULL- > LEXENV>) > 2: (SB-INT:SIMPLE-EVAL-IN-LEXENV (ITER (FOR I FROM 1 TO 10) > (COLLECT I)) #<NULL-LEXENV>) > 3: (SWANK::EVAL-REGION "(iter (for i from 1 to 10) > (collect i)) > " T) > 4: ((LAMBDA NIL)) > 5: ((SB-PCL::FAST-METHOD SWANK-BACKEND:CALL-WITH-SYNTAX-HOOKS > (T)) #<unused argument> #<unused argument> #<CLOSURE (LAMBDA NIL) > {119CD9E5}>) > 6: (SWANK::CALL-WITH-BUFFER-SYNTAX #<CLOSURE (LAMBDA NIL) > {119CD9E5}>) > 7: (SB-INT:SIMPLE-EVAL-IN-LEXENV (SWANK:LISTENER-EVAL "(iter (for > i from 1 to 10) > (collect i)) > ") #<NULL-LEXENV>) > 8: ((LAMBDA NIL)) > 9: ((SB-PCL::FAST-METHOD SWANK-BACKEND:CALL-WITH-DEBUGGER-HOOK (T > T)) #<unused argument> #<unused argument> #<FUNCTION SWANK:SWANK- > DEBUGGER-HOOK> #<CLOSURE (LAMBDA NIL) {119CD37D}>) > 10: ((LAMBDA NIL)) > 11: ((SB-PCL::FAST-METHOD SWANK-BACKEND:CALL-WITH-DEBUGGER-HOOK (T > T)) #<unused argument> #<unused argument> #<FUNCTION SWANK:SWANK- > DEBUGGER-HOOK> #<FUNCTION (LAMBDA NIL) {12870435}>) > 12: (SWANK::CALL-WITH-REDIRECTED-IO #<SWANK::CONNECTION {124976B1} > > #<CLOSURE (LAMBDA NIL) {119CA8AD}>) > 13: (SWANK::CALL-WITH-CONNECTION #<SWANK::CONNECTION {124976B1}> > #<FUNCTION (LAMBDA NIL) {12870435}>) > 14: (SWANK::HANDLE-REQUEST #<SWANK::CONNECTION {124976B1}>) > 15: (SWANK::PROCESS-AVAILABLE-INPUT #<SB-SYS:FD-STREAM for "a > constant string" {1286FFE1}> #<CLOSURE (LAMBDA NIL) {119CA895}>) > 16: ((FLET SWANK::HANDLER)) > 17: ((LAMBDA (SWANK-BACKEND::_)) #<unused argument>) > 18: (SB-IMPL::SUB-SERVE-EVENT NIL 0) > 19: (SB-SYS:WAIT-UNTIL-FD-USABLE 0 :INPUT NIL) > 20: (SB-IMPL::REFILL-BUFFER/FD #<SB-SYS:FD-STREAM for "standard > input" {1249A891}>) > 21: (SB-IMPL::INPUT-CHAR/UTF-8 #<SB-SYS:FD-STREAM for "standard > input" {1249A891}> NIL #:EOF-OBJECT) > 22: (READ-CHAR #<SB-SYS:FD-STREAM for "standard input" {1249A891}> > NIL #:EOF-OBJECT #<unused argument>) > 23: (READ-CHAR #<SYNONYM-STREAM :SYMBOL SB-SYS:*STDIN* {1000C9D1}> > NIL #:EOF-OBJECT #<unused argument>) > 24: (READ-CHAR #<SYNONYM-STREAM :SYMBOL SWANK::*CURRENT-STANDARD- > INPUT* {124970E9}> NIL #:EOF-OBJECT #<unused argument>) > 25: (READ-PRESERVING-WHITESPACE #<SYNONYM-STREAM :SYMBOL > SWANK::*CURRENT-STANDARD-INPUT* {124970E9}> NIL (NIL) T) > 26: (READ-PRESERVING-WHITESPACE #<SYNONYM-STREAM :SYMBOL > SWANK::*CURRENT-STANDARD-INPUT* {124970E9}> NIL (NIL) NIL) > 27: (READ #<SYNONYM-STREAM :SYMBOL SWANK::*CURRENT-STANDARD-INPUT* > {124970E9}> NIL (NIL) NIL) > 28: (SB-IMPL::REPL-READ-FORM-FUN #<SYNONYM-STREAM :SYMBOL > SWANK::*CURRENT-STANDARD-INPUT* {124970E9}> #<unavailable argument>) > 29: (SB-IMPL::REPL-FUN NIL) > 30: (SB-IMPL::REPL-FUN NIL) > 31: ((LAMBDA NIL)) > 32: ((LAMBDA NIL)) > 33: (SB-IMPL::%WITH-REBOUND-IO-SYNTAX #<CLOSURE (LAMBDA NIL) > {1249709D}>) > 34: (SB-IMPL::TOPLEVEL-REPL NIL) > 35: (SB-IMPL::TOPLEVEL-INIT) > 36: ((LABELS SB-IMPL::RESTART-LISP)) > -------------------------------------------------- Also, trying "(use-package :iter)", as suggested by Jorg Hohle, does not help: > -------------------------------------------------- > USE-PACKAGE #<PACKAGE "ITERATE"> causes name-conflicts in > #<PACKAGE "COMMON-LISP-USER"> between the following symbols: > ITERATE:FOR, FOR > [Condition of type SB-INT:NAME-CONFLICT] > > See also: > Common Lisp Hyperspec, 11.1.1.2.5 [section] > > Restarts: > 0: [RESOLVE-CONFLICT] Resolve conflict. > 1: [ABORT-REQUEST] Abort handling SLIME request. > 2: [ABORT] Exit debugger, returning to top level. > > Backtrace: > 0: (SB-INT:NAME-CONFLICT #<PACKAGE "COMMON-LISP-USER"> USE- > PACKAGE #<PACKAGE "ITERATE">) > 1: (USE-PACKAGE :ITER #<PACKAGE "COMMON-LISP-USER">) > 2: (SB-INT:SIMPLE-EVAL-IN-LEXENV (USE-PACKAGE :ITER) #<NULL-LEXENV>) > 3: (SWANK::EVAL-REGION "(use-package :iter) > " T) > 4: ((LAMBDA NIL)) > 5: ((SB-PCL::FAST-METHOD SWANK-BACKEND:CALL-WITH-SYNTAX-HOOKS > (T)) #<unused argument> #<unused argument> #<CLOSURE (LAMBDA NIL) > {12DEF7ED}>) > 6: (SWANK::CALL-WITH-BUFFER-SYNTAX #<CLOSURE (LAMBDA NIL) > {12DEF7ED}>) > 7: (SB-INT:SIMPLE-EVAL-IN-LEXENV (SWANK:LISTENER-EVAL "(use- > package :iter) > ") #<NULL-LEXENV>) > 8: ((LAMBDA NIL)) > 9: ((SB-PCL::FAST-METHOD SWANK-BACKEND:CALL-WITH-DEBUGGER-HOOK (T > T)) #<unused argument> #<unused argument> #<FUNCTION SWANK:SWANK- > DEBUGGER-HOOK> #<CLOSURE (LAMBDA NIL) {12DEF185}>) > 10: ((LAMBDA NIL)) > 11: ((SB-PCL::FAST-METHOD SWANK-BACKEND:CALL-WITH-DEBUGGER-HOOK (T > T)) #<unused argument> #<unused argument> #<FUNCTION SWANK:SWANK- > DEBUGGER-HOOK> #<FUNCTION (LAMBDA NIL) {118EABED}>) > 12: (SWANK::CALL-WITH-REDIRECTED-IO #<SWANK::CONNECTION {118BF9A9} > > #<CLOSURE (LAMBDA NIL) {12DEC9B5}>) > 13: (SWANK::CALL-WITH-CONNECTION #<SWANK::CONNECTION {118BF9A9}> > #<FUNCTION (LAMBDA NIL) {118EABED}>) > 14: (SWANK::HANDLE-REQUEST #<SWANK::CONNECTION {118BF9A9}>) > 15: (SWANK::PROCESS-AVAILABLE-INPUT #<SB-SYS:FD-STREAM for "a > constant string" {118EA761}> #<CLOSURE (LAMBDA NIL) {12DEC99D}>) > 16: ((FLET SWANK::HANDLER)) > 17: ((LAMBDA (SWANK-BACKEND::_)) #<unused argument>) > 18: (SB-IMPL::SUB-SERVE-EVENT NIL 0) > 19: (SB-SYS:WAIT-UNTIL-FD-USABLE 0 :INPUT NIL) > 20: (SB-IMPL::REFILL-BUFFER/FD #<SB-SYS:FD-STREAM for "standard > input" {118BF3B9}>) > 21: (SB-IMPL::INPUT-CHAR/UTF-8 #<SB-SYS:FD-STREAM for "standard > input" {118BF3B9}> NIL #:EOF-OBJECT) > 22: (READ-CHAR #<SB-SYS:FD-STREAM for "standard input" {118BF3B9}> > NIL #:EOF-OBJECT #<unused argument>) > 23: (READ-CHAR #<SYNONYM-STREAM :SYMBOL SB-SYS:*STDIN* {1000C9D1}> > NIL #:EOF-OBJECT #<unused argument>) > 24: (READ-CHAR #<SYNONYM-STREAM :SYMBOL SWANK::*CURRENT-STANDARD- > INPUT* {118BF299}> NIL #:EOF-OBJECT #<unused argument>) > 25: (READ-PRESERVING-WHITESPACE #<SYNONYM-STREAM :SYMBOL > SWANK::*CURRENT-STANDARD-INPUT* {118BF299}> NIL (NIL) T) > 26: (READ-PRESERVING-WHITESPACE #<SYNONYM-STREAM :SYMBOL > SWANK::*CURRENT-STANDARD-INPUT* {118BF299}> NIL (NIL) NIL) > 27: (READ #<SYNONYM-STREAM :SYMBOL SWANK::*CURRENT-STANDARD-INPUT* > {118BF299}> NIL (NIL) NIL) > 28: (SB-IMPL::REPL-READ-FORM-FUN #<SYNONYM-STREAM :SYMBOL > SWANK::*CURRENT-STANDARD-INPUT* {118BF299}> #<unavailable argument>) > 29: (SB-IMPL::REPL-FUN NIL) > 30: (SB-IMPL::REPL-FUN NIL) > 31: ((LAMBDA NIL)) > 32: ((LAMBDA NIL)) > 33: (SB-IMPL::%WITH-REBOUND-IO-SYNTAX #<CLOSURE (LAMBDA NIL) > {118BF15D}>) > 34: (SB-IMPL::TOPLEVEL-REPL NIL) > 35: (SB-IMPL::TOPLEVEL-INIT) > 36: ((LABELS SB-IMPL::RESTART-LISP)) > -------------------------------------------------- I hope my problem is trivial. Many thanks for your consideration in helping me find it, Olivier Drolet

2 1

[iterate-devel] destructively altering elements
by Albert Krewinkel 27 Jun '07

27 Jun '07

Hello, I'm doing some matrix operations and would like to use iterate for going through my matrices element wise. Writing an driver to do this was pretty easy (great tools and manual!), but it doesn't allow me to alter entries in my matrix. Therefore I was wondering if there is some easy way to write something like (FOR el IN-MATRIX vec) that expands to (symbol-macrolet ((el (aref vec row-index col-index))) (... body...)) If there is no way to do this, could you please provide me with some pointers about how I can contribute to add such feature? Thanks in advance Albert Note: I asked this question on comp.lang.lisp and was redirected here. For the corresponding thread see http://groups.google.de/group/comp.lang.lisp/browse_thread/thread/007e48775… -- Albert Krewinkel <krewink (at) inb.uni-luebeck.de> University of Luebeck, Institute for Neuro- and Bioinformatics http://www.inb.uni-luebeck.de/~krewink/

2 4

[iterate-devel] Sequence variables are initialized twice
by Bruno Daniel 21 Jun '07

21 Jun '07

Dear developers, the following example shows that iter initializes sequence variables twice, once with 0 and once with the start of the range minus 1. (macroexpand-1 '(iter (for i below 10) (print i))) --> (LET* ((I 0)) (DECLARE (TYPE NUMBER I)) (BLOCK NIL (TAGBODY (SETQ I -1) LOOP-TOP-NIL (SETQ I (+ I 1)) (IF (>= I 10) (GO LOOP-END-NIL)) (PRINT I) (GO LOOP-TOP-NIL) LOOP-END-NIL) NIL)) The problem with this is not that this is a little bit ugly but that one must allow negative values in declarations for the driver variable, which conflicts with (unsigned-byte 32) declarations. Could I write a new driver instead of for that fixes the problem or will I run into trouble because someteimes one of the initial values is needed for something else (the else clause, first-time-p or initially?). Moreover, the declaration is not very tight. dotimes does better on SBCL: (macroexpand-1 '(dotimes (i 10) (print i))) --> (DO ((I 0 (1+ I))) ((>= I 10) NIL) (DECLARE (TYPE UNSIGNED-BYTE I)) (PRINT I)) Best regards Bruno Daniel

3 3

[iterate-devel] PATCH: support (finding (values ...))
by Max Mikhanosha 11 Jun '07

11 Jun '07

Hi, I was optimizing my code and noticed that I got a bunch of brute force searches for an extremum of a function of more then one value like so: (bind (((best-x best-y best-z) (iter outer (for x ...) (iter (for y ...) (iter (for z ...) (in outer (finding (list x y z) maximizing (objective x y z)))))))) ...) The above code is causing excessive consing in the (list x y z) part and one can't specify (values) instead. With the attached patch I can write: (bind (((values best-x best-y best-z) (iter outer (for x ...) (iter (for y ...) (iter (for z ...) (in outer (finding (values x y z) maximizing (objective x y z)))))) ...) which does not cons and results in faster code. Regards, Max

2 3

[iterate-devel] Request to mailing list elephant-devel rejected
by elephant-devel-bounces＠common-lisp.net 30 May '07

30 May '07

Your request to the elephant-devel mailing list Posting of your message titled "[SPAM] TIM SURPRESA PARA VOC�!!!" has been rejected by the list moderator. The moderator gave the following reason for rejecting your request: "No reason given" Any questions or comments should be directed to the list administrator at: elephant-devel-owner(a)common-lisp.net

1 0

[iterate-devel] Request to mailing list elephant-devel rejected
by elephant-devel-bounces＠common-lisp.net 30 May '07

30 May '07

Your request to the elephant-devel mailing list Posting of your message titled "[SPAM] TIM SURPRESA PARA VOC�!!!" has been rejected by the list moderator. The moderator gave the following reason for rejecting your request: "No reason given" Any questions or comments should be directed to the list administrator at: elephant-devel-owner(a)common-lisp.net

1 0

[iterate-devel] Your message to cl-muproc-devel awaits moderator approval
by cl-muproc-devel-bounces＠common-lisp.net 29 May '07

29 May '07

Your mail to 'cl-muproc-devel' with the subject [SPAM] TIM SURPRESA PARA VOC�!!! Is being held until the list moderator can review it for approval. We're sorry, due to the volume of spam we receive most mailinglists require you to subscribe before posting. You may cancel this post (at the URL below) or waiting for the moderator to approve it. Thanks and sorry for the inconvenience. The reason it is being held: Message has implicit destination Either the message will get posted to the list, or you will receive notification of the moderator's decision. If you would like to cancel this posting, please visit the following URL: http://common-lisp.net/cgi-bin/mailman/confirm/cl-muproc-devel/6082b0de352a…

1 0

[iterate-devel] Your message to cl-darcs-devel awaits moderator approval
by cl-darcs-devel-bounces＠common-lisp.net 29 May '07

29 May '07

Your mail to 'cl-darcs-devel' with the subject [SPAM] TIM SURPRESA PARA VOC�!!! Is being held until the list moderator can review it for approval. We're sorry, due to the volume of spam we receive most mailinglists require you to subscribe before posting. You may cancel this post (at the URL below) or waiting for the moderator to approve it. Thanks and sorry for the inconvenience. The reason it is being held: Message has implicit destination Either the message will get posted to the list, or you will receive notification of the moderator's decision. If you would like to cancel this posting, please visit the following URL: http://common-lisp.net/cgi-bin/mailman/confirm/cl-darcs-devel/971a91fddcdf8…

1 0

[iterate-devel] Your message to cffi-devel awaits moderator approval
by cffi-devel-bounces＠common-lisp.net 29 May '07

29 May '07

Your mail to 'cffi-devel' with the subject [SPAM] TIM SURPRESA PARA VOC�!!! Is being held until the list moderator can review it for approval. We're sorry, due to the volume of spam we receive most mailinglists require you to subscribe before posting. You may cancel this post (at the URL below) or waiting for the moderator to approve it. Thanks and sorry for the inconvenience. The reason it is being held: Message has implicit destination Either the message will get posted to the list, or you will receive notification of the moderator's decision. If you would like to cancel this posting, please visit the following URL: http://common-lisp.net/cgi-bin/mailman/confirm/cffi-devel/b5f476e05b1e5d923…

1 0