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

[alexandria-devel] EXTREMUM
by Tobias C Rittweiler 25 Apr '12

25 Apr '12

The cl-utilities library contains one function which cannot be found in alexandria that necessity pops up every now and then: Returning the maximum (or minimum) element in a sequence with respect to an arbitrary calculation involving the elements. I.e. (elt (sort (copy-sequence <SEQUENCE>) #'< :key <FUNCTION>) 0) ; or #'> except doing it more efficiently. CL-UTILITIES calls this function EXTREMUM. (It also provides a couple of more functions along the lines to cover some edge cases.) The code can be found here: http://common-lisp.net/viewvc/cl-utilities/cl-utilities/extremum.lisp?rev ision=1.10&view=markup As the code is Public Domain, it could just be moved as is. I find no other use of cl-utilities and would like to see it become entirely obsolete. T

2 3

[alexandria-devel] Some number patches
by Robert Smith 25 Apr '12

25 Apr '12

Hello all: I've decided I'm going to try to merge in stuff from my QTILITY library [1] in an attempt to reduce the number of utility libraries out there -- provided the stuff fits with the goals of Alexandria. Xach and I decided it's best not to add more utility libraries to Quicklisp. I've created a patch that adds MULF and DIVF, which do what you might expect (modify macros for * and /). I also added some numerical predicates that I myself like, as well as others: POSITIVEP, NEGATIVEP, NON-POSITIVE-P, NON-NEGATIVE-P, NON-ZERO-P. As you might notice, they sound especially familiar to those who read mathematics literature. Also, would it be possible for me to have push permissions? I hope you'll take these attached patches into consideration. Thanks, Robert Smith [1] https://bitbucket.org/tarballs_are_good/qtility/src

4 4

[alexandria-devel] test failures on ACL and CMUCL
by Anton Vodonosov 22 Apr '12

22 Apr '12

Hello. I wander if it's a known issue that alexandria tests fail on ACL and CMUCL? (there also failures on CLISP, but they are marked as "known failres" in the test suite) For you convenience here is the list of failed tests and what compilers are affected by each failure (from the test results we collected on the recent Quicklisp): "alist-hash-table.1" => ("clisp-2.49+-unix") "copy-hash-table.1" => ("acl-8.2a-linux-x64" "clisp-2.49+-unix") "copy-sequence.1" => ("cmu-20c_release-20c__20c_unicode_-linux-x86") "plist-hash-table.1" => ("clisp-2.49+-unix") "type=.3" => ("acl-8.2a-linux-x64") "type=.4" => ("acl-8.2a-linux-x64") More information (with the test run logs where more details may be found): http://common-lisp.net/project/cl-test-grid/pivot_lib_ql-lisp.html Best regards, - Anton

3 3

[alexandria-devel] [PATCH] PROG1-LET
by Benjamin Saunders 12 Apr '12

12 Apr '12

PROG1-LET is a binding macro modeled closely after WHEN-LET and friends, which I have regularly found useful in code to implement the "create, modify, return" pattern common in some imperative code. As a simple and, I believe, widely useful macro, I'd like to see this enter into Alexandria proper. Docstring follows: Creates new variable bindings and executes FORMS, returning the initial value of the first binding. BINDINGS must be either single binding of the form: (variable initial-form) or a list of bindings of the form: ((variable initial-form) (variable-2 initial-form-2) ... (variable-n initial-form-n)) All initial-forms are executed sequentially in the specified order, then all the variables are bound to the corresponding values and FORMS are executed as an implicit PROGN. Finally, the value returned by INITIAL-FORM is returned.

5 12

[alexandria-devel] Reminder alexandria:curry is not currying
by Tomohiro Matsuyama 12 Apr '12

12 Apr '12

Hi, Is there any progress on this discussion? http://www.mail-archive.com/alexandria-devel@common-lisp.net/msg00199.html I really won't use `curry' as partial application. I hope `partial-apply' will be soon available. -- Tomohiro Matsuyama <tomo(a)cx4a.org>

4 6

Re: [alexandria-devel] Some problem with alexandria
by Zach Beane 08 Apr '12

08 Apr '12

Juan Jose Garcia-Ripoll <juanjose.garciaripoll(a)googlemail.com> writes: > This wasn't happening before. Seems some upgrade of quicklisp pulled a version > with this tiny bug. ECL is a bit picky about the order of arguments in LOOP. I > will change this to a warning in the next release, though. Does the latest version of alexandria in source control fix things? I intend to release a new update today and it would be nice if it was working properly. Zach

2 1

[alexandria-devel] broken LOOP forms
by Greg Pfeil 30 Mar '12

30 Mar '12

Alexandria (QL version) doesn't compile on ECL and warns on CLISP because invalid LOOP forms are used in (at least) COPY-STREAM. EG: (loop :while (< input-position start) :for bytes-read = (read-sequence buffer input :end (min (length buffer) (- start input-position))) :do (progn (when (zerop bytes-read) (error "Could not read enough bytes from the input to fulfill the START requirement in ~S" 'copy-stream)) (incf input-position bytes-read))) And I _think_ according to http://www.lispworks.com/documentation/HyperSpec/Body/m_loop.htm, the :WHILE expression can't precede the :FOR expression.

2 1

[alexandria-devel] destructuring-case
by Jasper 30 Mar '12

30 Mar '12

Hello all, The `destructuring-case` macro imo is a little different than I would think it would be upon just hearing the name. The thing is, i'd have made the clauses to basically the `destructuring-bind` form, except that a clause is executed if the 'nested lists-shape' matches, and all non-symbols, keywords match. I'd add `quote` as special, something that also must match exactly, and maybe `lambda`/`function` to indicate a function that must return true.(which now i think of it is an idea for the next section.) (shameless plug)Maybe the reason is that i wrote a `destructuring-regex` https://github.com/o-jasper/j-basic/blob/master/src/destructuring-regex.lisp of which the idea is that the variables can simply be written on the matches/space between the matches.(Further each lisp object can add a method giving the regular expression for it, and also provide a parser) It uses the regex package though, is cl-ppcre more commonly used as dependency? But basically, i have a `regex-case` for it. Them being regexes and either matching or not make it obvious how that should work! Looking at the git log it was added Sep23 2010, so i am probably too late to change `destructuring-case`? I dont know, i see there are no official releases, and it might sneakily be that many people are using the link from the cliki page!(from 2008) - Ending a hopefully not too inane post, Jasper

2 1

[alexandria-devel] #'shuffle docstring is misleading
by Orivej Desh 30 Mar '12

30 Mar '12

#'shuffle docstring states that “Permuted sequence may share storage with the original one.” Actually it destructively modifies the sequence. In the case of vectors the two might be the same, but in the case of lists I would say that something like (sort (copy-list l) …) shares storage with the original list but (sort l …) does more than that.

2 1

[alexandria-devel] reverting patch
by Tamas Papp 30 Mar '12

30 Mar '12

Hi, I have been trying to reach Nikodemus Siivola for a while but didn't get a response, so I thought I would write here hoping that someone can help me. Nikodemus admitted my "generic MEAN and MEDIAN, new function DISPLACE-ARRAY" patch to Alexandria 11 days ago. This was meant to be an initial patch, followed by others, with the final goal of making mean, median and variance generic. The first patch dealt with MEAN and MEDIAN. I would like to ask that this patch is removed from Alexandria for the time being, for the following two reasons: 1. The generic variance I wrote would not support the :BIASED keyword, in fact, only "unbiased" variance makes sense in certain situations. Since :BIASED T is the default, this would break existing code in a silent manner, which is not desirable. 2. The new function DISPLACE-ARRAY is badly designed: the keyword defaults handle what turns out to be a rarely used corner case for me. I would rather keep the old functionality, already present in CL-NUM-UTILS. I am sorry for the confusion. I think it is best if I experiment within my own libraries for a while before re-addressing these issues. I wonder if someone could revert the patch, preferably soon, so that the next release of Quicklisp would contain Alexandria without my code. Best, Tamas

2 1