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

[iterate-devel] iterate 1.3?
by Marco Baringer 22 Feb '05

22 Feb '05

1) antifuchs recently gave me write access to the iterate project on common-lisp.net. i'd like to use my new power to create a new release of iterate (there's been a lot of work since 1.3pre1). anybody have problems with this? 2) i'd like to commit the latest set of iterate patches to the arch repo, what's the "best" version of iterate lying around. i'm guessing this is jorg's but i'd like to make sure no one else has other fixes lying around. -- -Marco Ring the bells that still can ring. Forget the perfect offering. There is a crack in everything. That's how the light gets in. -Leonard Cohen

2 1

Re: [iterate-devel] destructuring-bind bug
by Hoehle, Joerg-Cyril 18 Feb '05

18 Feb '05

Hi, >The following form never terminates. >(macroexpand '(iter (for index in '((1 2))) (collect >(destructuring-bind (a b) index (+ a b))))) My version of Iterate not only macroexpands, but it also executes it and yields (3) in CLISP-2.33.some-CVS on Linux, meeting my expectations. For Iterate, it's very important to say which Lisp implementation you're using, since it heavily depends on macroexpansion. Expansion of typical CL macros differ a lot among implementations and this is known to have caused different behaviour of Iterate across implementations. Also, you did not say which version you're using. Please submit details, e.g. Lisp version, what does destructuring-bind macroexpand-1 to, etc. Or forget about this trouble, and merely update Iterate. I believe it's also included with Marc Battyani's cl-pdf and Marco Baringer's UCW and/or arnesi packages. Regards, Jörg Höhle.

2 1

[iterate-devel] destructuring-bind bug
by Julian Stecklina 17 Feb '05

17 Feb '05

Hello, The following form never terminates. (macroexpand '(iter (for index in '((1 2))) (collect (destructuring-bind (a b) index (+ a b))))) Regards, Julian Stecklina __________________________________________________________ Mit WEB.DE FreePhone mit hoechster Qualitaet ab 0 Ct./Min. weltweit telefonieren! http://freephone.web.de/?mc=021201

1 0

[iterate-devel] thereis and always/never conflict revisited
by Hoehle, Joerg-Cyril 07 Feb '05

07 Feb '05

Hi, I've been thinking about this way of removing the ambiguity of contradicting defaults for always/never and thereis. CLtL2's loop thereis does not mention a default. ANSI-CL does. My reading of CLtL2 is compatible with an implementation of thereis as `when expr return it' -- no default value is supplied. Maybe CLtL2 didn't mention it because the default return of loop is NIL anyway, but who knows? Now, I propose to implement thereis in Iterate exactly like this. Benefit: o Some meaning associated to a form previously rejected as ambiguous (always/never with thereis). empty iterations with always+thereis would yield T. o thereis can be used with any other clause, including collect, always etc. Drawback: o Some meaning associated to a form previously rejected as ambiguous :) and which formally, still is ambiguous. This is precisely why e.g. Bruno Haible rejected a change to CLISP's loop -- which also rejects always+thereis as erroneous -- that I suggested some month ago. Indeed, the form is still ambiguous from a mathematical POV. ALWAYS and THEREIS do not really fit together. Am I sacrificing too much for too little gain? E.g., my proposed thereis could be rewritten as a macro: `(let ((,var ,expr)) (if ,var (leave ,var))) so, when that's needed, the user could do it themselves. Regards, Jorg Regards, Jorg Hohle.

1 0

[iterate-devel] how to generate pdf from tex?
by Hoehle, Joerg-Cyril 01 Feb '05

01 Feb '05

Hi, I've been able to generate a .pdf from a .tex in a non-straight-forward way, so I'm wondering how it should actually be done. 1. using pdf or latex (dvi output), TeX will complain about the missing iter-man.ind file. o Where does it come from? o is there an easy substitute (instead of using null.tex/sty)? I used iter-man.idx instead, but this was not understood by the pdftex driver 2. pdftex pdftex iter-man -> error about \documentstyle pdfvirtex &pdfcslatex iter-man (I found the dir with the pdfcslatex.fmt and other .fmt in my Suse 8.1 distribution in /var/lib/..., but no pdflatex.fmt) works, after adding symlink of pdftex.cfg into the current directory The table of content did not generate clickable entries, nor bookmarks. I thought this was the big advantage of using pdftex? dvipdf iter-man.dvi generated a .pdf (smaller in size), this uses dvips internally, and a %pdf-1.3 header, while pdftex generates %pdf-1.4 Both appear with similar quality on screen, is that normal? I included that .pdf from pdfcslatex in the distribution I can send on request (see previous e-mail of mine, from today). Regards, Jorg Hohle.

1 0

[iterate-devel] more bug-fixes available
by Hoehle, Joerg-Cyril 01 Feb '05

01 Feb '05

Hi, I have fixed some more bugs or problem areas in my copy of iterate, and I can send that to anybody who wishes. You may want to try the following test in your original version: (deftest or.1 (iter (generate x in '(a nil nil 1)) (generate y in-vector '#(2 #\c #\d)) (collect (or (next x) (next y)))) (a 2 #\c 1)) >From my changes file: o (if (next x) ...) works -- the test form is walked too + allow better compiler optimizations by keeping macros like and, or, prog1 etc. in the expanded code. The expansion also becomes more readable (closer to the source). + #+clisp support ((setf foo) new-value args...) function syntax + #+clisp simple support for handler-bind (not walking handlers) + free-vars correctly handles locally, symbol-macrolet and declare + use macroexpand-1 only to ensure all special handlers get used and still more test cases Marco, I don't know how you modified your UCW and CPS converter for use with CLISP, but I recommend you do not use sys::setf-... (clisp internals) -- I'm not even sure your patch works in all conceivable cases. I don't know what the requirements for ucw/cps are, but here's what I use for iterate: #+clisp ; some macros expand into ((setf foo) value other-args...) ;; reported by Marco Baringer on 24 Jan 2005 ((typep form '(cons (cons (eql setf) *) *)) (apply #'walk-cdr form)) You can see that the setf form is treated like any other function call, and there's no need to make use of (possibly changing) internals. Things I changed previously are: o (DSETQ (values x nil y)) works o restore v 1.0/2 special/macro order, e.g. change special-form? etc. o in-vector/in-sequence downwards by 2 did not start with last element (iter (for i index-of-vector #(0 1 2 3 4) downto 0 by 2) (collect i)) yielded (3 1), expect (4 2 0) by similarity with (iter (for i downfrom 4 by 2) (collect i)) and (iter (for i from 4 downto 0 by 2) (collect i)) + locally accepts [0..N] declarations + constant? and self-evaluating? accept all self-evaluating forms, including keywords and T/NIL, but no other symbols. + avoid ~< pretty-printer (not in Cormanlisp) in error messages, leave that to the implementation + if-1st-time & special-clause ELSE: type 'boolean instead of symbol + #+clisp "explicit declarations are always placed in the generated code" as the manual says. + #+lispworks multiple-value-bind is recognized (again) + make-next-code N <> 1 generates correct code Regards, Jorg Hohle

1 0

Re: [iterate-devel] clisp setf wark around
by Hoehle, Joerg-Cyril 25 Jan '05

25 Jan '05

Hi, Marco Baringer wrote: >This (5 line) patch deals with clisp's ((setf foo) value other-args). Thanks for pointing out the problem. I wrote to clisp-list about it. Do you have a testcase? How did you find out about this bug? >+ (walk `(funcall ',(get (second (car form)) 'system::setf-function) I'll soon submit a patch for Iterate which also works with [9]> (macroexpand-1'(setf (values-list (list a b c)) (foo))) (LET* ((#:G6359 (LIST A B C))) ((SETF VALUES-LIST) (FOO) #:G6359)) ; T which your's doesn't (looking up internals from sys::setf-function is not a good idea). I would probably use walk-cdr or some such. Regards, Jorg Hohle

2 1

Re: [iterate-devel] clisp setf wark around
by Hoehle, Joerg-Cyril 24 Jan '05

24 Jan '05

Thanks for the bug report. Marco wrote: >bese-2004(a)common-lisp.net/iterate--clisp-setf--1.0--patch-1 Great, but do you have an idea how I can look at that 5-liner? My connection to the internet is via a firewall, so I can't use specific protocols (like CVS, unless tunelled by ssh), nor does GNUArch (not installed) help me. By looking around URLs, I found browseable (pseudo-?)directories like but no trace of your patch. All files there are from September 2004. http://common-lisp.net/project/iterate/iterate-devel@common-lisp.net--2004/… Regards, Jorg Hohle.

2 1

[iterate-devel] clisp setf wark around
by Marco Baringer 23 Jan '05

23 Jan '05

bese-2004(a)common-lisp.net/iterate--clisp-setf--1.0--patch-1 This (5 line) patch deals with clisp's ((setf foo) value other-args). -- -Marco Ring the bells that still can ring. Forget the perfect offering. There is a crack in everything. That's how the light gets in. -Leonard Cohen

1 0

[iterate-devel] Re: handler-bind macroexpansion and special operators (fwd)
by Hoehle, Joerg-Cyril 18 Jan '05

18 Jan '05

Hi, Sam Steingold wrote: >The only place where it occurs is HANDLER-BIND which is a standard >macro though, so I suggest that ITERATE handles HANDLER-BIND specially, >not via MACROEXPAND. That's indeed needed for Iterate, ouch! But that's only one issue. Every program or library which does code-walking and comes across IGNORE-ERRORS or HANDLER-BIND in CLISP will barf on this. Having a useful response from SPECIAL-OPERATOR-P would at least help these to correctly recognize the situation at hand. Which is the second issue: I believe a bug in CLISP's special-operator-p. Regards, Jorg Hohle

3 4