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

Patch for iterate.asd
by Robert P. Goldman 21 Apr '17

21 Apr '17

ASDF no longer is happy with system names like "iterate-test". Instead, subsidiary systems in the same .asd file should be named using a slash. So, "iterate/test". As a bonus in exchange for the need to rename, ASDF will now be able to find all the subsidiary systems. I.e., you can simply do (asdf:load-system "iterate/test") now, instead of (asdf:load-system "iterate) (asdf:load-system "iterate-test") which was necessary before, because until ASDF had loaded "iterate" it didn't know where to look for the definition of "iterate-test." At the same time I killed the block comment at the top, which was a complaint about ASDF that is no longer current (the feature requested has been added). I'm afraid darcs is one revision control system too many for my poor brain (any chance of changing the iterate repo to git?), so I am attaching a patch file that can be applied to iterate.asd.

2 2

.asd file IN-PACKAGE
by Robert P. Goldman 12 Jul '16

12 Jul '16

The ASD file is IN-PACKAGE ASDF, which is really not A Good Thing. You could at least potentially damage a user's working ASDF by smashing some symbol in that package. The comment at the header expresses a dislike for adding a new package. That's fine. If you don't put a package there, ASDF will load it into ASDF-USER. So we should either: 1. replace ASDF with ASDF-USER in the IN-PACKAGE -- that's what I would favor, since it allows a programmer to interact with this definition in the editor or 2. simply remove the IN-PACKAGE form altogether, and ASDF will automagically put it into an appropriate package. Best, r

2 3

License terms for ITERATE
by Robert P. Goldman 08 Jul '16

08 Jul '16

ITERATE has a GPL license. Does that mean that the developers intend that any system using ITERATE must, itself, be GPL? I am not certain what follows from GPL licensing, since Lisp code isn't linked with library code. But I fear it might, or might require some cumbersome expedient like forcing people who distribute non-GPL code to hand off the ITERATE code and require recipients to compile it in themselves. Is there any chance that this could be offered under LLGPL or some less-restrictive license? Thanks, r

1 1

usage with ECL on Android
by Helmut Jarausch 17 Apr '15

17 Apr '15

Hi, I just have a binary for ECL on my Android phone but no other Lisp infrastructure. How can I use iterate under these circumstances? Many thanks for a hint, Helmut

1 0

Re: [Iterate-devel] iterate-1.4.3 doesn't compile under SBCL-1.2.8
by Zach Kost-Smith 25 Feb '15

25 Feb '15

I do see the same error and cannot build Iterate 1.4.3, but that was all a bit of a surprise. That is because I use Iterate every day and trust that it will always work, and it has, if you are using the Quicklisp version of the library. So to you, Helmut, I would suggest that you start using Quicklisp (http://www.quicklisp.org/) and bask in the limited amount of quality control that it has. The bigger question here is what is going on with darcs/current tarball/Quicklisp? You don't see this problem with Quicklisp version of iterate, which should be taken from the darcs repo automatically on regular periods. So I cloned the darcs repo and (other than some misterious "hash failed" errors) it is identical to the quicklisp version and, naturally, it loads fine. The last time the quicklisp version was updated was sometime in June of last year which is after the last commit in the log of the darcs repo (on April 22: "make the #L reader macro standard conformant by not assuming anything about the representation of quasiquoted forms") . So what is 1.4.3? A diff between the Quicklisp version and the 1.4.3 version shows that there are substantial changes. I really don't know much about Darcs, but I assume that there is some other branch out there or something which is where "1.4.3" resides. Is this a rogue or development branch that somebody is accidentally giving as the current version on common-lisp.net? Zach KS On Wed, Feb 25, 2015 at 6:02 AM, Helmut Jarausch <jarausch(a)skynet.be> wrote: > Hi, > > please bear in mind that I'm Lisp newbee. > When I try to load iterate (1.4.3) I get the warnings and one error below. > > Many thanks for a hint, > Helmut > > > ; in: DEFMACRO WITH-TEMPORARY > ; `(LET ((,ITERATE::OLD-VAR ITERATE::*TEMPS-IN-USE*)) > ; (UNWIND-PROTECT > ; (LET ,(MAPCAR #'(LAMBDA # `#) ITERATE::VARS) > ; . ,ITERATE::BODY) > ; (SETQ ITERATE::*TEMPS-IN-USE* ,ITERATE::OLD-VAR))) > ; --> SB-IMPL::|List| SB-IMPL::|List| SB-IMPL::|List*| MAPCAR LET LET > ; --> SB-INT:DO-ANONYMOUS BLOCK LET TAGBODY TAGBODY SB-KERNEL:%RPLACD > ; --> SETQ THE LIST CONS > ; ==> > ; (SB-C::%FUNCALL #:G2 (CAR #:G1)) > ; > ; caught WARNING: > ; function called with one argument, but wants exactly zero > ; See also: > ; The ANSI Standard, Section 3.2.2.3 > > ; file: /home/jarausch/Lisp_My/TEST/iterate.lisp > ; in: DEFMACRO WITH-TEMPORARY > ; `(LET ((,ITERATE::OLD-VAR ITERATE::*TEMPS-IN-USE*)) > ; (UNWIND-PROTECT > ; (LET ,(MAPCAR #'(LAMBDA # `#) ITERATE::VARS) > ; . ,ITERATE::BODY) > ; (SETQ ITERATE::*TEMPS-IN-USE* ,ITERATE::OLD-VAR))) > ; --> SB-IMPL::|List| SB-IMPL::|List| SB-IMPL::|List*| MAPCAR LET > ; --> SB-KERNEL:%COERCE-CALLABLE-TO-FUN FUNCTION SB-INT:QUASIQUOTE > ; ==> > ; (SB-IMPL::|List*| ITERATE::!1 '((ITERATE::GET-FREE-TEMP))) > ; > ; caught WARNING: > ; undefined variable: !1 > ; > > The following errors occurs in several functions > > ; in: DEFUN RETURN-COLLECTION-CODE > ; (ITERATE::WITH-TEMPORARY ITERATE::TEMP-VAR > ; (LET* ((ITERATE::UPDATE-CODE > ; `(IF ,ITERATE::COLLECT-VAR > ; # > ; #)) > ; (ITERATE::MAIN-CODE (COND # # #))) > ; (ITERATE::RETURN-CODE :BODY > ; `((PROGN > ; ,.ITERATE::MAIN-CODE > ; ,ITERATE::COLLECT-VAR)) > ; :FINAL > ; (IF (EQ ITERATE::RESULT-TYPE 'LIST) > ; NIL > ; `(#))))) > ; > ; caught ERROR: > ; during macroexpansion of > ; (WITH-TEMPORARY TEMP-VAR > ; (LET* # > ; #)). > > > _______________________________________________ > Iterate-devel mailing list > Iterate-devel(a)common-lisp.net > https://mailman.common-lisp.net/cgi-bin/mailman/listinfo/iterate-devel >

1 0

[Iterate-devel] iterate-1.4.3 doesn't compile under SBCL-1.2.8
by Helmut Jarausch 25 Feb '15

25 Feb '15

Hi, please bear in mind that I'm Lisp newbee. When I try to load iterate (1.4.3) I get the warnings and one error below. Many thanks for a hint, Helmut ; in: DEFMACRO WITH-TEMPORARY ; `(LET ((,ITERATE::OLD-VAR ITERATE::*TEMPS-IN-USE*)) ; (UNWIND-PROTECT ; (LET ,(MAPCAR #'(LAMBDA # `#) ITERATE::VARS) ; . ,ITERATE::BODY) ; (SETQ ITERATE::*TEMPS-IN-USE* ,ITERATE::OLD-VAR))) ; --> SB-IMPL::|List| SB-IMPL::|List| SB-IMPL::|List*| MAPCAR LET LET ; --> SB-INT:DO-ANONYMOUS BLOCK LET TAGBODY TAGBODY SB-KERNEL:%RPLACD ; --> SETQ THE LIST CONS ; ==> ; (SB-C::%FUNCALL #:G2 (CAR #:G1)) ; ; caught WARNING: ; function called with one argument, but wants exactly zero ; See also: ; The ANSI Standard, Section 3.2.2.3 ; file: /home/jarausch/Lisp_My/TEST/iterate.lisp ; in: DEFMACRO WITH-TEMPORARY ; `(LET ((,ITERATE::OLD-VAR ITERATE::*TEMPS-IN-USE*)) ; (UNWIND-PROTECT ; (LET ,(MAPCAR #'(LAMBDA # `#) ITERATE::VARS) ; . ,ITERATE::BODY) ; (SETQ ITERATE::*TEMPS-IN-USE* ,ITERATE::OLD-VAR))) ; --> SB-IMPL::|List| SB-IMPL::|List| SB-IMPL::|List*| MAPCAR LET ; --> SB-KERNEL:%COERCE-CALLABLE-TO-FUN FUNCTION SB-INT:QUASIQUOTE ; ==> ; (SB-IMPL::|List*| ITERATE::!1 '((ITERATE::GET-FREE-TEMP))) ; ; caught WARNING: ; undefined variable: !1 ; The following errors occurs in several functions ; in: DEFUN RETURN-COLLECTION-CODE ; (ITERATE::WITH-TEMPORARY ITERATE::TEMP-VAR ; (LET* ((ITERATE::UPDATE-CODE ; `(IF ,ITERATE::COLLECT-VAR ; # ; #)) ; (ITERATE::MAIN-CODE (COND # # #))) ; (ITERATE::RETURN-CODE :BODY ; `((PROGN ; ,.ITERATE::MAIN-CODE ; ,ITERATE::COLLECT-VAR)) ; :FINAL ; (IF (EQ ITERATE::RESULT-TYPE 'LIST) ; NIL ; `(#))))) ; ; caught ERROR: ; during macroexpansion of ; (WITH-TEMPORARY TEMP-VAR ; (LET* # ; #)).

1 0

[Iterate-devel] iterate on list bug?
by Gábor Balázs 21 May '14

21 May '14

hY, I have a feeling this is a bug. (defvar mylist '(:one :two :three)) (iter (for var on mylist) (collect (car var) into result) (finally (return (values result var)))) (:ONE :TWO :THREE) (:THREE) I think var should be empty at the end, so the result would match the result of loop as (loop for var on mylist collect (car var) into result finally (return (values result var))) (:ONE :TWO :THREE) NIL The problem is caused by the end test code location. The bold lines should appear in reverse order, I think. (macroexpand-1 '(iter (for var on mylist) (collect (car var) into result) (finally (return (values result var))))) (LET* ((#:LIST214 NIL) (VAR NIL) (RESULT NIL) (#:END-POINTER215 NIL) (#:TEMP216 NIL)) (BLOCK NIL (TAGBODY (PROGN (SETQ #:LIST214 MYLIST)) LOOP-TOP-NIL (PROGN * (IF (ATOM #:LIST214) (GO LOOP-END-NIL)) (SETQ VAR #:LIST214)* (SETQ #:LIST214 (CDR #:LIST214)) (PROGN (SETQ #:TEMP216 (LIST (CAR VAR))) (SETQ #:END-POINTER215 (IF RESULT (SETF (CDR #:END-POINTER215) #:TEMP216) (SETQ RESULT #:TEMP216))) RESULT)) (PROGN) (GO LOOP-TOP-NIL) LOOP-END-NIL (PROGN (RETURN (VALUES RESULT VAR)))) NIL)) Best, ` bg`

3 4

Re: [Iterate-devel] [Sbcl-devel] pprinter regression
by Attila Lendvai 23 Apr '14

23 Apr '14

(i'm CC'ing this mail to iterate-devel to notify people there also. please only reply-all to this mail if you intend to send your reply to iterate-devel also.) On Wed, Apr 23, 2014 at 8:02 AM, Douglas Katzman <dougk(a)google.com> wrote: > Attached is a patch for 'iterate'. Hopefully someone on this list can patch > that it. thanks, i've pushed the patch into the official iterate repo. Wed Apr 23 10:47:59 ALMT 2014 Douglas Katzman <dougk(a)google.com> * make the #L reader macro standard conformant by not assuming anything about the representation of quasiquoted forms. -- • attila lendvai • PGP: 963F 5D5F 45C7 DFCD 0A39 -- “Being really good at C++ is like being really good at using rocks to sharpen sticks.” — Thant Tessman

1 0

[iterate-devel] small feature request w/ patch
by Ryan Davis 04 Jan '13

04 Jan '13

I'm trying to organize my workplace lisp libraries (from a cobble of source checkouts and asdf-installed stuff), and we had a small patch to iterate that I'd like in the mainline so we can consume iterate via quicklisp. It adds a new restart in #'ambiguity-check-clause to delete one of the clauses to resolve the ambiguity. This has been very helpful when developing and debugging new iterate drivers, and I don't think it has any other relevant effects. Attached is a dpatch created with `darcs send -O`, but if that doesn't work here's the diff: diff -rN old-iterate/iterate.lisp new-iterate/iterate.lisp 1322c1322,1323 < (error "Iterate: Inserting clause ~a would create ~ --- > (restart-case > (error "Iterate: Inserting clause ~a would create ~ 1324c1325,1328 < kw1 kw2)))) --- > kw1 kw2) > (delete-conflict () > :report "Delete the original clause" > (remove-clause kw2)))))) Thanks, -- Ryan Davis Acceleration.net Director of Programming Services 2831 NW 41st street, suite B Gainesville, FL 32606 Office: 352-335-6500 x 124 Fax: 352-335-6506

2 1

[iterate-devel] Bug with (collect :at :beginning)
by psexton.2a＠gmail.com 13 Dec '12

13 Dec '12

When collecting values into a list, if the first value collected uses (collect val :at :beginning), and a subsequent value does not use the ":at :beginning" clause, then an error will occur: "The value nil is not of type cons". The following reproduces this error: (iterate (for i from 1 to 10) (if (oddp i) (collect i :at :beginning) (collect i)))

1 0