- pro - mailman3.common-lisp.net

macro returning more than one form
by Paul Tarvydas 14 Mar '14

14 Mar '14

What is the best way to write a macro that returns more than one form to the top level? E.g. (in-package :xxx) (defun ...) I've been wrapping a progn around the result, but LW doesn't like it very much, and SBCL seems to hate it. Thanks pt

8 15

Testing and concurrency
by Eli Naeher 14 Mar '14

14 Mar '14

Hello, Recently I've begun writing tests which need to do things in several threads. I'm curious as to what approaches other people have taken when doing this, and whether any of the CL test frameworks address this situation specifically. Some of the things I've run into: - detecting, handling, and reporting conditions that are raised in threads other than the main test/reporting thread - ensuring that the main test thread waits for the other threads before checking for the correct results (and before returning) - forcing things in different threads to happen at the same time (I've been using SBCL's timers for this) Any thoughts or pointers toward best-practices here would be appreciated. Thank you, -Eli

3 2

[CfP] DEADLINE EXTENSION - 7th European Lisp Symposium
by Didier Verna 11 Mar '14

11 Mar '14

ELS'14 - 7th European Lisp Symposium IRCAM, Paris, France May 5-6, 2014 http://www.european-lisp-symposium.org/ Sponsored by IRCAM, CNRS, UPMC, EPITA, LispWorks, Franz Inc. Latest News: * SUBMISSION DEADLINE EXTENDED. You have two more week to submit! * Registration is now open. Early registration fee until April 13. See http://www.european-lisp-symposium.org/content-registration-full.html The purpose of the European Lisp Symposium is to provide a forum for the discussion and dissemination of all aspects of design, implementation and application of any of the Lisp and Lisp-inspired dialects, including Common Lisp, Scheme, Emacs Lisp, AutoLisp, ISLISP, Dylan, Clojure, ACL2, ECMAScript, Racket, SKILL, Hop and so on. We encourage everyone interested in Lisp to participate. The 7th European Lisp Symposium invites high quality papers about novel research results, insights and lessons learned from practical applications, and educational perspectives. We also encourage submissions about known ideas as long as they are presented in a new setting and/or in a highly elegant way. Topics include but are not limited to: - Context-, aspect-, domain-oriented and generative programming - Macro-, reflective-, meta- and/or rule-based development approaches - Language design and implementation - Language integration, inter-operation and deployment - Development methodologies, support and environments - Educational approaches and perspectives - Experience reports and case studies Please note that IRCAM, the conference venue, is a French institute for research on music and acoustics. Submissions relating Lisp to music or other acoustical matters will hence be particularly welcome, although given no heightened favor during the review process. We invite submissions in the following forms: Papers: Technical papers of up to 8 pages that describe original results or explain known ideas in new and elegant ways. Demonstrations: Abstracts of up to 2 pages for demonstrations of tools, libraries, and applications. Tutorials: Abstracts of up to 4 pages for in-depth presentations about topics of special interest for at least 90 minutes and up to 180 minutes. The symposium will also provide slots for lightning talks, to be registered on-site every day. All submissions should be formatted following the ACM SIGS guidelines and include ACM classification categories and terms. For more information on the submission guidelines and the ACM keywords, see: http://www.acm.org/sigs/publications/proceedings-templates and http://www.acm.org/about/class/1998. Important dates: - TODAY: Mark your calendar. Start planning now! - 23 Mar 2014: Submission deadline **** EXTENDED **** - 31 Mar 2014: Notification of acceptance - 13 Apr 2014: Early registration deadline - 21 Apr 2014: Final Papers due - 05 May 2014: Symposium. Join us there! Programme chair: Kent Pitman, Hypermeta Inc., U.S.A. Local chairs: Didier Verna, EPITA Research Lab, France Gérard Assayag, IRCAM, Paris, France Programme committee: Marie Beurton-Aimar — LaBRI, University of Bordeaux, France Pierre Parquier — IBM France Lab, Paris, France Rainer Joswig — Hamburg, Germany Guiseppe Attardi — Università di Pisa, Italy Taiichi Yuasa — Kyoto University, Japan António Leitão — IST/Universidade de Lisboa, Portugal Christophe Rhodes — Goldsmiths, University of London, UK Olin Shivers — Northeastern University, USA Charlotte Herzeel — IMEC, ExaScience Life Lab, Leuven, Belgium Local organizers: Daniela Becker, EPITA Research Lab, France Sylvie Benoit, IRCAM, Paris, France Search Keywords: #els2014, ELS 2014, ELS '14, European Lisp Symposium 2014, European Lisp Symposium '14, 7th ELS, 7th European Lisp Symposium, European Lisp Conference 2014, European Lisp Conference '14 Ircam STMS Lab, IRCAM / CNRS / UPMC -- Resistance is futile. You will be jazzimilated. Lisp, Jazz, Aïkido: http://www.didierverna.info

1 0

Why Lisp is Now an Acceptable Scripting Language
by Faré 03 Mar '14

03 Mar '14

My cl-launch demo: cl -sp lisp-stripper -i '(print-loc-count "asdf.lisp")' Source code for lispwc: #!/usr/bin/cl -sp lisp-stripper -E main (defun main (argv) (if argv (map () 'print-loc-count argv) (print-loc-count *standard-input*))) And of course: for l in sbcl ccl clisp cmucl ecl abcl \ scl allegro lispworks gcl xcl ; do cl-launch -l $l -i \ '(format t "'$l': ~S~%" `#5(1 ,@`(2 3)))' \ 2>&1 | grep "^$l:" # LW, GCL are verbose done Backstory: After recent exposure to Python at work, I grew an intense dislike for that language, and realized that I could do everything in CL instead, and that the remaining stumbling blocks to using CL as a "scripting language" were quite small — just missing the ability to put #!/usr/bin/cl in a script, and there you go. And so, I added just this capability to cl-launch, improved it to have some of the features of buildapp, and made sure it works without a hitch on each of the 11 implementations with a command-line interface. This in turn requires updating ASDF and UIOP, and so here we are with ASDF 3.1.0.86. Then, I found that I had to take the word out, and started editing that way a paper that I'm preparing a paper for ELS 2014 (or else ILC 2014): ASDF3, or Why Lisp is Now an Acceptable Scripting Language It's incredible how having to explain the code forces you to make it actually simpler to use. Hence new option -sp in cl-launch, to load a system and change the current package, all in one go. Hence also having cl-launch build software with a sequence of --system --load --eval instead of a single setup file and toplevel system like before: people already understand a sequence of build commands. Also new in ASDF3: command line argument support was improved with a LispWorks workaround and a new argv0 function; with-input and with-output accept pathnames as designating a file to open; the bundle support was much improved and cleaned up; the upgrade mechanism was slightly improved to cope with the class refactoring; bugs were found and removed in pathname functions; a weird bug in SCL was worked around. Enjoy! TODO: I'm considering modifying the default behavior of cl-launch to launch a REPL and/or read commands from stdin, like a Unix shell does when given no script and no commands to run. I'm reserving that for another round of procrastination. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org To have a right to do a thing is not at all the same as to be right in doing it. — G.K. Chesterton

2 2

Demographics of lisp users
by Matthew Swank 16 Feb '14

16 Feb '14

Are there any good resources about what kinds of people are (currently) using lisp?

2 1

ELS 2014 Registration now open / 2nd Call for papers
by Didier Verna 11 Feb '14

11 Feb '14

ELS'14 - 7th European Lisp Symposium IRCAM, Paris, France May 5-6, 2014 http://www.european-lisp-symposium.org/ Latest News: * Registration is now open. Early registration fee until April 13. See http://www.european-lisp-symposium.org/content-registration-full.html * Submission deadline is approaching. Still one month to submit a paper! * Thanks to our new sponsors, Lispworks and Franz Inc.! http://www.lispworks.com/ http://franz.com/ The purpose of the European Lisp Symposium is to provide a forum for the discussion and dissemination of all aspects of design, implementation and application of any of the Lisp and Lisp-inspired dialects, including Common Lisp, Scheme, Emacs Lisp, AutoLisp, ISLISP, Dylan, Clojure, ACL2, ECMAScript, Racket, SKILL, Hop and so on. We encourage everyone interested in Lisp to participate. The 7th European Lisp Symposium invites high quality papers about novel research results, insights and lessons learned from practical applications, and educational perspectives. We also encourage submissions about known ideas as long as they are presented in a new setting and/or in a highly elegant way. Topics include but are not limited to: - Context-, aspect-, domain-oriented and generative programming - Macro-, reflective-, meta- and/or rule-based development approaches - Language design and implementation - Language integration, inter-operation and deployment - Development methodologies, support and environments - Educational approaches and perspectives - Experience reports and case studies Please note that IRCAM, the conference venue, is a French institute for research on music and acoustics. Submissions relating Lisp to music or other acoustical matters will hence be particularly welcome, although given no heightened favor during the review process. We invite submissions in the following forms: Papers: Technical papers of up to 8 pages that describe original results or explain known ideas in new and elegant ways. Demonstrations: Abstracts of up to 2 pages for demonstrations of tools, libraries, and applications. Tutorials: Abstracts of up to 4 pages for in-depth presentations about topics of special interest for at least 90 minutes and up to 180 minutes. The symposium will also provide slots for lightning talks, to be registered on-site every day. All submissions should be formatted following the ACM SIGS guidelines and include ACM classification categories and terms. For more information on the submission guidelines and the ACM keywords, see: http://www.acm.org/sigs/publications/proceedings-templates and http://www.acm.org/about/class/1998. Important dates: - TODAY: Mark your calendar. Start planning now! - 09 Mar 2014: Submission deadline - 31 Mar 2014: Notification of acceptance - 13 Apr 2014: Early registration deadline - 21 Apr 2014: Final Papers due - 05 May 2014: Symposium. Join us there! Programme chair: Kent Pitman, Hypermeta Inc., U.S.A. Local chairs: Didier Verna, EPITA Research Lab, France Gérard Assayag, IRCAM, Paris, France Programme committee: To be announced later Local organizers: Daniela Becker, EPITA Research Lab, France Sylvie Benoit, IRCAM, Paris, France Search Keywords: #els2014, ELS 2014, ELS '14, European Lisp Symposium 2014, European Lisp Symposium '14, 7th ELS, 7th European Lisp Symposium, European Lisp Conference 2014, European Lisp Conference '14 Ircam STMS Lab, IRCAM / CNRS / UPMC -- Please help crowdfund my next Jazz quartet album !! http://www.kisskissbankbank.com/quartet-the-second-album Lisp, Jazz, Aïkido: http://www.didierverna.info

1 0

Congruence of lamda-lists of methods with their generic-function
by Jean-Claude Beaudoin 09 Feb '14

09 Feb '14

Hello CL Pros, I am trying to understand the meaning in conforming ANSI CL of the following code snippet and I am not quite sure what to think of it: (defgeneric foo (a b &key)) (defmethod foo (a b &key c d) (or c d 42)) At this point should a call to foo accept any keyword argument, no keyword argument or only :c and/or :d? What would be the outcome of this: (foo 1 2 :d 3) Is it an error being signaled or the value 3 being returned? I am inclined to believe that an error should be signaled, since the generic function lambda-list contains no explicit keyword argument and no &allow-other-keys. Reading CLHS 7.6.4 it seems to me that (defgeneric foo (a b &key)) and (defgeneric foo (a b &key &allow-other-keys)) are two different things as to the set of keyword arguments they each will accept. The first one being the empty set and the second the set of all possible sequence of keyword arguments (limits set aside). Am I right? Also if I go for (defgeneric (a b &key &allow-other-keys)), is the lambda-list of the method as here above still congruent? Doesn't it need to be rewritten as: (defmethod foo (a b &key c d &allow-other-keys) ...) or (defmethod foo (a b &rest other-args) ...) to be properly congruent? Thanks, Jean-Claude Beaudoin

5 4

loop conformance
by Steve Haflich 30 Jan '14

30 Jan '14

I'm in a grumpy mood today, so I decided to take out my frustrations on the ANS for CL, or implementations thereof. Consider carefully what the following form should return: (let ((v (make-array 10 :initial-contents '(0 1 2 3 4 5 6 7 8 9) :fill-pointer 5))) (loop for x across v when (eql x 2) do (incf (fill-pointer v)) collect x)) ACL and SBCL both return (0 1 2 3 4). Probably every other implementation does too. I believe the ANS requires the return to be (0 1 2 3 4 5), although the definition in *6.1.2.1.5 The for-as-across subclause* uses various undefined terminology. (We of X3J13 understood that the loop specification was not our best work.)

7 10

Fwd: ASDF walkthrough
by Faré 25 Jan '14

25 Jan '14

Reminder for those who knew, late announcement for the others: the ASDF walkthrough will happen on Google Hangouts tomorrow Sunday 2014-01-26 from 1400 to 1600 EST (1900 to 2100 UTC). If you want to attend and didn't register yet, send me a personal email specifying which hangout address I should invite tomorrow. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org The older I grow, the more I distrust the familiar doctrine that age brings wisdom. — H.L. Mencken On Fri, Jan 3, 2014 at 2:10 AM, Faré <fahree(a)gmail.com> wrote: > Dear Lisp hackers, > > I'm considering recording a walk through the ASDF sources. > > I'd like to have an interactive session over Google Hangout > with one or a few people, explaining the current code in asdf/defsystem > (i.e. not going into uiop, except to minimally explain what asdf uses). > That should take about 2 hours. > > To enjoy the walkthrough, you need to be somewhat fluent in Common Lisp, > and somewhat familiar with how to use ASDF, though not necessarily with > either extending it or hacking its internals. > > If at least one person is familiar with ASDF 2 and has questions, > that could be interesting, or that could be a separate session. > > Please respond me to this email (privately or publicly) if you're interested. > > —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org > We are always in anarchy. But we pay a hefty price maintaining the illusion > that we aren't, and another one being misled by the illusion.

1 0

Fwd: ASDF walkthrough
by Faré 04 Jan '14

04 Jan '14

Dear Lisp hackers, I'm considering recording a walk through the ASDF sources. I'd like to have an interactive session over Google Hangout with one or a few people, explaining the current code in asdf/defsystem (i.e. not going into uiop, except to minimally explain what asdf uses). That should take about 2 hours. To enjoy the walkthrough, you need to be somewhat fluent in Common Lisp, and somewhat familiar with how to use ASDF, though not necessarily with either extending it or hacking its internals. If at least one person is familiar with ASDF 2 and has questions, that could be interesting, or that could be a separate session. Please respond me to this email (privately or publicly) if you're interested. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org If a trainstation is where the trains stop, what is then a workstation... — Lars Lundgren <d95lars(a)dtek.chalmers.se>

12 13