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

[iterate-devel] Proposal for manual modification re defclause-sequence
by Mirko Vukovic 12 Feb '10

12 Feb '10

Hello, I recently had an issue of saving iterate extension code in sbcl fasl files. Several folks have commented that the documentation on defclause-sequency could be more explicit on that topic. Thus this email. You can find the whole email thread here: http://common-lisp.net/pipermail/iterate-devel/2010-February/000654.html (the first email in that thread has an attachment with the original problem file). Basically the problem was the following defclause-sequence definition: (defclause-sequence matrix-row matrix-row-index :access-fn (lambda (grid index) (assert (and (grid:gridp grid) (eql (grid:grid-rank grid) 2)) (grid)) (grid:row grid index)) :size-fn (lambda (grid) (assert (and (grid:gridp grid) (eql (grid:grid-rank grid) 2)) (grid)) ... etc. In an interpreted list, such as clisp, there were no problems with this form. But in a compiled list, such as sbcl, the form could be evaluated, but could not be saved in a fasl. Thus compile file and asdf loading did not work. The solution was to quote the lambda forms: (defclause-sequence matrix-row matrix-row-index :access-fn '(lambda (grid index) (assert (and (grid:gridp grid) (eql (grid:grid-rank grid) 2)) (grid)) (grid:row grid index)) :size-fn '(lambda (grid) (assert (and (grid:gridp grid) (eql (grid:grid-rank grid) 2)) (grid)) ... etc. Important to note, sharp-quoting -- #' -- such as in the example code in the manual, did not work. My (very incomplete understanding) is that storing lists (such as '(lambda ...) in fasl's is OK, and iter can figure out what to do with them once read back in. But not storing compiled objects (which a #'(lambda ...) cannot be stored in fasl's. I propose that the documentation be changed, with perhaps a few additional examples. I would be glad to work with one of the developers/maintainers off-line on this issue. Regards, Mirko

1 0

[iterate-devel] Fwd: iterate form evaluates but does not load into sbcl fasl
by Mirko Vukovic 09 Feb '10

09 Feb '10

Hello, (A copy of this email was recently sent to the gsll and sbcl mailing lists). The package gsd <http://repo.or.cz/w/gsd.git>, part of gsll<http://common-lisp.net/project/gsll/>uses iterate to loop over elements of vectors and matrices. I have attached the part of the package that extends iterate to this email. I am having the following issue on sbcl1.034 on RHEL5 64-bit linux, via slime. The following form evaluates OK at the REPL. (iter:iter (iter:for c :matrix-row grid::*array-3-4-double-float* ) (print c)) But, if I embed it into a function: (defun foo () (iter:iter (iter:for c :matrix-row grid::*array-3-4-double-float*) (print c))) it will evaluate OK in slime (C-x C-e), but will not compile (C-c C-c). The returned error is: >>> post-processing/xpdp-post-processing.lisp:75:3: error: Objects of type FUNCTION can't be dumped into fasl files. --> LET* BLOCK TAGBODY PROGN SETQ THE FUNCALL SB-C::%FUNCALL THE --> SB-KERNEL:%COERCE-CALLABLE-TO-FUN ==> #<FUNCTION (LAMBDA #) {1002DD7AD9}> note: The first argument never returns a value. --> LET* BLOCK TAGBODY PROGN SETQ THE FUNCALL SB-C::%FUNCALL THE ==> (SB-KERNEL:%COERCE-CALLABLE-TO-FUN #<FUNCTION # {1002DD7AD9}>) ... more stuff >>> So, it seems that sbcl can digest it, but for some reason cannot write it to a fasl. The macroexpansion of the code above is: (LET* ((#:SEQUENCE120 NIL) (#:LIMIT121 NIL) (C NIL) (#:INDEX119 NIL)) (BLOCK NIL (TAGBODY (PROGN (SETQ #:SEQUENCE120 GRID::*ARRAY-3-4-DOUBLE-FLOAT*) (SETQ #:LIMIT121 (FUNCALL # #:SEQUENCE120)) (SETQ #:INDEX119 -1)) LOOP-TOP-NIL (PROGN (SETQ #:INDEX119 (+ #:INDEX119 1)) (IF (>= #:INDEX119 #:LIMIT121) (GO LOOP-END-NIL)) (SETQ C (FUNCALL # #:SEQUENCE120 #:INDEX119)) (PRINT C)) (PROGN) (GO LOOP-TOP-NIL) LOOP-END-NIL (PROGN)) NIL)) Is this issue due to a malformed extension of iterate, or some misalignment between iterate and sbcl? Thank you, Mirko

4 7

[iterate-devel] Problem with iterate and fare-matcher
by Olof-Joachim Frahm 05 Feb '10

05 Feb '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I've got a problem using iterate with the fare-matcher library (both current versions). In the following code fragment, the function FOO does as it should, matching for the symbol QUIT from the current package. The function BAR however only wraps it inside the iterate macro and then apparently produces slightly wrong code: > (use-package '(#:fare-matcher #:iterate)) > > (defun foo (msg) > (match msg > ('quit 42) > (_ 'else))) > > (foo 'quit) > ;; 42 > > (defun bar (msg) > (iterate > (leave (match msg > ('quit 42) > (_ 'else))))) > > (bar 'quit) > ;; ELSE > (bar 'fare-matcher::quit) > ;; 42 Even with macroexpanding the two definitions I couldn't figure out where this goes wrong, so maybe you have an idea about this. Cheers, Olof - -- Es liegt in der menschlichen Natur, unvenrüntfig zu denken und zu handeln. -- nach Anatole France -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (GNU/Linux) iEYEARECAAYFAktsY3kACgkQEiTh585nXwB3jgCeNh5pUyV5D2g5f41z6iA5zJoc lkIAn3ULA6Jy0JKDjKWLi3Q1wXsAzvag =4EaR -----END PGP SIGNATURE-----

1 0