March 2010 - alexandria-devel - mailman3.common-lisp.net

[alexandria-devel] Review cycle 2: SWITCH, ESCWITCH, and CSWITCH
by Nikodemus Siivola 08 Apr '10

08 Apr '10

macro switch ((object &key test key) &body clauses) "Evaluates first matching clause, returning its values, or evaluates and returns the values of DEFAULT if no keys match." macro eswitch ((object &key test key) &body clauses) "Like SWITCH, but signals an error if no key matches." cswitch ((object &key test key) &body clauses) "Like SWITCH, but signals a continuable error if no key matches."

8 23

[alexandria-devel] Lost earmuff in tests.lisp
by Peter Graves 11 Mar '10

11 Mar '10

diff -rN -u old-alexandria/tests.lisp new-alexandria/tests.lisp --- old-alexandria/tests.lisp 2009-10-07 03:51:00.000000000 -0700 +++ new-alexandria/tests.lisp 2009-10-07 03:51:01.000000000 -0700 @@ -7,7 +7,7 @@ (in-package :alexandria-tests) -(defun run-tests (&key ((:compiled *compile-tests))) +(defun run-tests (&key ((:compiled *compile-tests*))) (do-tests)) ;;;; Arrays

2 1

[alexandria-devel] Optimization for whichever
by Gustavo 11 Mar '10

11 Mar '10

Hello, I have optimized the expansion of the macro whichever. In the current implementation, it generates n random values, creates O(n) functions and calls one of them. Using a sort of "inline" binary search, I was able to create an expansion which makes one call to RANDOM, O(log n) tests, and also does not create any extra function. A test with my implementation: cl-user> (macroexpand-1 '(whichever (list 1) (list 2) (list 3) (list 4) (list 5) (list 6) (list 7))) (let ((#:random-number854 (random 7))) (if (< #:random-number854 3) (if (< #:random-number854 1) (list 1) (if (< #:random-number854 2) (list 2) (list 3))) (if (< #:random-number854 5) (if (< #:random-number854 4) (list 4) (list 5)) (if (< #:random-number854 6) (list 6) (list 7))))) t Regards, Gustavo Henrique Milaré.

4 3

[alexandria-devel] Alexandria in Git!
by Nikodemus Siivola 09 Mar '10

09 Mar '10

Everything should be in working order now, and the webpage has been updated as well. (I did not convert the Darcs repo that holds the webpage history yet.) I consider the Darcs repository frozen at this point, but if someone has stuff in Darcs against it, I can handle conversion to Git -- I just need to pull URL for Darcs. Preferred submission format is IMO output from git format-patch. Cheers, -- Nikodemus

1 0

[alexandria-devel] Alexandria in git?
by Nikodemus Siivola 08 Mar '10

08 Mar '10

I made a tentative gitified Alexandria repo, up at http://github.com/nikodemus/alexandria Would moving to git inconvenience people, aside from one-time switch-related issues? I personally find git *much* more convenient to work with -- but this is very likely just due to knowing it far better than Darcs. This is not about relative merits of Darcs and Git, but about convenience for people involved. I'm pretty sure either one is plenty "good enough" for Alexandria per se. Cheers, -- Nikodemus

3 4

[alexandria-devel] Possible WITH-COLLECTOR/COLLECTORS macros
by Daniel White 08 Mar '10

08 Mar '10

This has particularly useful when dealing with mapping functions for variously libraries. Not sure whether this falls into the scope of Alexandria or not, but I find myself reaching for it often enough that it would be nice to have. The other question is whether the plural version is really necessary or whether the singular version could be left out in favour of the plural version. Personally, I've only had use for the singular version. I've attached a patch that includes docstrings and some tests, but I've placed the implementations inline for easy perusal/discussion. (defmacro with-collector ((name) &body forms) (with-unique-names (list-head list-tail) `(let* ((,list-head (list nil)) (,list-tail ,list-head)) (flet ((,name (object) (rplacd ,list-tail (setq ,list-tail (list object))) object)) ,@forms (cdr ,list-head))))) (defmacro with-collectors ((&rest names) &body forms) (let ((name-gensyms (make-gensym-list (length names)))) (labels ((%expand-collectors (names name-gensyms) (if names `(setf ,(car name-gensyms) (with-collector (,(car names)) ,(%expand-collectors (cdr names) (cdr name-gensyms)))) `(progn ,@forms)))) `(let ,name-gensyms ,(%expand-collectors names name-gensyms) (values ,@name-gensyms))))) Basic usage is simply: (with-collector (collect) (dotimes (x 4) (collect x))) => '(0 1 2 3) Regards, -- Daniel White

5 7

[alexandria-devel] [patch] documentation tweak
by Daniel Herring 08 Mar '10

08 Mar '10

Hi all, Would you consider applying the attached patch? It fixes an obscure nuisance when generating the documentation. Thanks, Daniel

2 1

[alexandria-devel] Maintenance
by Tobias C. Rittweiler 04 Mar '10

04 Mar '10

Hi folks! I had this idea to ask implementators how they'd feel inclined about including Alexandria as part of their implementations as most nowadays do with ASDF. For that to work, of course, there has to be Alexandria releases, and once something's officially released, backwards-compatiblity would have to be preserved. (I think there should be an official ALEXANDRIA package containing the stable API, and some -TESTBED or -BETA package with stuff being in flux, but for people to try out who are so inclined. Together with some ALEXANDRIA-VERSION<= stuff for conditionalization.) I'd offer to step up, polish the existing code base, write tests where needed, write documentation, do releases, and try to push the things down the implementations. I'd hope that the quality of my existing libraries speak for how severe I take all these steps to produce well-rounded releases. Nowadays, it's my impression that the only somewhat active people are Nikodemus and Attila, where Nikodemus seems to hold the power of ultimate decision making. There are probably more who feel strongly about Alexandria so I wanted to ask you first, because it'd mean a shift of responsibility and power. What do you think? -T.

2 1

[alexandria-devel] Maintenance
by Tobias C. Rittweiler 03 Mar '10

03 Mar '10

Hi folks! I had this idea to ask implementators how they'd feel inclined about including Alexandria as part of their implementations as most nowadays do with ASDF. For that to work, of course, there has to be Alexandria releases, and once something's officially released, backwards-compatiblity would have to be preserved. (I think there should be an official ALEXANDRIA package containing the stable API, and some -TESTBED or -BETA package with stuff being in flux, but for people to try out who are so inclined. Together with some ALEXANDRIA-VERSION<= stuff for conditionalization.) I'd offer to step up, polish the existing code base, write tests where needed, write documentation, do releases, and try to push the things down the implementations. I'd hope that the quality of my existing libraries speak for how severe I take all these steps to produce well-rounded releases. Nowadays, it's my impression that the only somewhat active people are Nikodemus and Attila, where Nikodemus seems to hold the power of ultimate decision making. There are probably more who feel strongly about Alexandria so I wanted to ask you first, because it'd mean a shift of responsibility and power. What do you think? -T.

4 4