alexandria-devel December 2009

alexandria-devel@common-lisp.net

1 participants
3 discussions

[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] eval-always, defun-always, etc...
by Attila Lendvai 03 Dec '09

03 Dec '09

dear list, i know that this is a subject that has strong feelings attached to, but with recent developments in XCVB the need for (eval-when (:compile-toplevel :load-toplevel :execute) ...) has rose, and seeing numerous eval-when noise in the code is potentially annoying. related material: a) relevant part of XCVB docs: http://common-lisp.net/project/xcvb/doc/README.html#compile-time-side-effec… b) "XCVB patch for Alexandria" thread on alexandria-devel c) blog entry from Nikodemus at http://random-state.net/log/3387124996.html (broken currently, google cache below) http://209.85.129.132/search?q=cache:dmgWWKN8vFMJ:random-state.net/log/3387… ============= c) makes it clear that Nikodemus doesn't like eval-always, and i'm sure many other lispers are on the same opinion. for the argument that it does not introduce a new abstraction, i can point to COND, which is the same as an ugly IF ladder, still most people prefer COND when there are many legs of that if, because in that case COND is much less noisy. no new abstraction, only a syntactic sugar, but it's much easier for the eye. a) has a detailed description why often a full (:compile-toplevel :load-toplevel :execute) is necessary, and it'll be even more so as XCVB gets used more and more. so, i'd suggest to take some action: I) add an eval-always to alexandria-devel II) add a defun-always to alexandria-devel avoid the entire need for a wrapper III) ? my vote goes for II), which is kinda in sync with c) too. suggestions? opinions? -- attila

7 12

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

alexandria-devel December 2009