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

[iterate-devel] iterate package source code server
by Hoehle, Joerg-Cyril 12 Nov '04

12 Nov '04

Hi, it's a great idea to put valuable but old packages from the AI repository or whereever to an open source server on the net! I've done several changes that I'll release soon, but there are are a few points I'd like to discuss before: o Participation: GNUArch to me sounds like yet another CVS system. It causes me overhead as I have to install yet anoter SW on the PC. CVS, subversions, GNUArch, where will it end? Is that really necessary? o "to quote or not to quote" -- see separate e-mail. Here's a list of changes which I've done so far: o minor CL optimizations: consp, pop, export, declaim o for in-package(s) evaluates package(s) argument o for in-package(s) works as generator o for in-hashtable usable as generator o for in-hashtable supports destructuring o for in-packages was broken because of 'pkgs symbol-types are not evaluated in with-package-iterator and must not be empty => consp o (for vars DO-NEXT) now binds vars o use dsetq instead of destructuring-bind for consistency of templates + (code-char 0) is portable, #\nul or #\null is not + use #:start/beginning to (hopefully) work with Allegro modern style + tiny changes to manual o added more testcases Planned: support (dsetq (values x nil y) (foo)) to ignore second value Regards, Jörg Höhle.

2 1

[iterate-devel] iterate proposal: "maybe quote or not" is bad design: remove from manual
by Hoehle, Joerg-Cyril 11 Nov '04

11 Nov '04

Hi, I'd like to change the few places where the manual says "may be quoted, but need not be". Rationale: don't make the user believe something is evaluated when it's not! Despite the manual says so, (collect i at 'beginning) barfs. Instead of changing the code to make this work, I propose to change the manual to *not* accept quoted forms. 1. These confuse the user. They fool the user into believing arbitrary forms could be used (if (foo) 'beginning 'end) and that it's a run-time choice when it's not. 2. These make implementations contain broken heuristics like (and consp (eq car 'quote)) I believe there's more value in making such forms accept various forms of symbols (like loop keywords), e.g. :end, end END etc. instead. On a similar issue, I have criticized UFFI for containing similar heuristics instead of clear descriptions of what types are evaluated and what not (cf. uffi-users list of October 2004). Kevin Rosenberg is about to change something there. Cost of change to users: it's a pure matter of style. Users using 'end/'beginning/'start need to use other forms, e.g. (collect foo :at :start) (collect foo at :start) (collect foo :at #:start) (collect foo #:at start) etc. All of these can be supported cheaply (in terms of run-time) and I'm sure all users will find a form that pleases them visually. Prior to making these changes in (my copy of) the code, I wanted to discuss the issue at first. Regards, Jörg Höhle

1 0

[iterate-devel] Bug in "the type" expansion?
by rif 31 Oct '04

31 Oct '04

According to page 20 of the September 2004 version of the manual, I would expect (iter (for (the fixnum n) in '(3 5 7 8 9)) (counting (oddp n))) to expand into a form in which n was declared/guaranteed fixnum. It does not. It binds n to nil initially, and (therefore?) omits the declaration. (iter (for n in '(3 5 7 8 9)) (declare (fixnum n)) (counting (oddp n))) does the right thing. Cheers, rif

3 2

[iterate-devel] iterate for emacs lisp?
by Chris Newcombe 13 Oct '04

13 Oct '04

(re-send, as it was bounced last time) Hi, (Apologies if this is a FAQ -- I don't know of any archive for this list.) Is iterate available for emacs lisp? (I'm using FSF Emacs v21.2). I imagine that the latest version of the common-lisp extensions for emacs lisp would be required, but is that enough to get it to work? Many thanks for maintaining this excellent package! regards, Chris Newcombe

3 2

[iterate-devel] Iterate broken on ACL 7.0 beta?
by Arthur Lemmens 29 Sep '04

29 Sep '04

Hi, I just downloaded iterate 1.0.9 from common-lisp.net and tried it with ACL 7.0 beta. Unfortunately, I get a stack overflow error (see the backtrace below) when I do the following: 1. compile (and load) package.lisp and iterate.lisp 2. evaluate (in-package iterate) 3. try out the example from the readme (iterate (generate i from 0 to 6) (for (key . value) in '((a . 2) (zero . 10) (one . 20) (d . 5))) (when (>= value 10) (collect (cons key (next i))))) This is not critical for me (I'll just use an older version of iterate that I've been using for the last 4 years and that has no problems with your example or with my programs in general), but I thought you might want to know this. Sorry that I don't come with a fix, but I don't have the time for debugging this right now. Regards, Arthur --------- Stack overflow (signal 1000) [Condition of type EXCL:SYNCHRONOUS-OPERATING-SYSTEM-SIGNAL] Restarts: 0: [CONTINUE] continue computation 1: [ABORT] Abort handling SLIME request. 2: [ABORT] Abort entirely from this (lisp) process. Backtrace: 0: (SWANK::DEBUG-IN-EMACS #<EXCL:SYNCHRONOUS-OPERATING-SYSTEM-SIGNAL @ #x20888ea2>) 1: ((FLET SWANK:SWANK-DEBUGGER-HOOK SWANK::DEBUG-IT)) 2: (SWANK:SWANK-DEBUGGER-HOOK #<EXCL:SYNCHRONOUS-OPERATING-SYSTEM-SIGNAL @ #x20888ea2> #<Function SWANK-DEBUGGER-HOOK>) 3: (CERROR "continue computation" EXCL:SYNCHRONOUS-OPERATING-SYSTEM-SIGNAL :FORMAT-CONTROL "Stack overflow (signal 1000)" :FORMAT-ARGUMENTS NIL) 4: (SPECIAL-OPERATOR-P :UNKNOWN) 5: (SYSTEM:FUNCTION-INFORMATION COND NIL) 6: (MACROEXPAND-1 (COND ((>= VALUE 10) NIL (COLLECT (CONS KEY (NEXT I))))) NIL) 7: (MACROEXPAND (COND ((>= VALUE 10) NIL (COLLECT (CONS KEY (NEXT I))))) NIL) 8: (WALK (COND ((>= VALUE 10) NIL (COLLECT (CONS KEY (NEXT I))))) NIL) 9: (WALK (COND ((>= VALUE 10) NIL (COLLECT (CONS KEY (NEXT I))))) NIL) 10: (WALK (COND ((>= VALUE 10) NIL (COLLECT (CONS KEY (NEXT I))))) NIL) 11: (WALK (COND ((>= VALUE 10) NIL (COLLECT (CONS KEY (NEXT I))))) NIL) 12: (WALK (COND ((>= VALUE 10) NIL (COLLECT (CONS KEY (NEXT I))))) NIL) 13: (WALK (COND ((>= VALUE 10) NIL (COLLECT (CONS KEY (NEXT I))))) NIL) 14: (WALK (COND ((>= VALUE 10) NIL (COLLECT (CONS KEY (NEXT I))))) NIL) 15: (WALK (COND ((>= VALUE 10) NIL (COLLECT (CONS KEY (NEXT I))))) NIL) 16: (WALK (COND ((>= VALUE 10) NIL (COLLECT (CONS KEY (NEXT I))))) NIL)

2 2