March 2014 - pro - mailman3.common-lisp.net

Formal Presentation and initial doubts.
by Alejandro Zamora Fonseca 11 Apr '14

11 Apr '14

Hello for everybody!!. My name is alejandro and I'm a new Common Lisp fan. I've been use it almost 1 year and I think is an awesome language. But I have some troubles with topics, like GUI for desktop apps, and Unicode characters. I use Clisp mainly, ECL, and Clozure CL too. Would you help me with some hints for these problems? Greetings, Alejandro -- Este mensaje le ha llegado mediante el servicio de correo electronico que ofrece Infomed para respaldar el cumplimiento de las misiones del Sistema Nacional de Salud. La persona que envia este correo asume el compromiso de usar el servicio a tales fines y cumplir con las regulaciones establecidas Infomed: http://www.sld.cu/

8 9

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

19 Mar '14

@All, thanks for the interesting discussion. Certainly gives me something to chew on. Re-reading the responses, I see that, while I did sort-of say it, I didn't emphasize the point of this: I have a PEG-syntax parser written in esrap. I am binding at least two such parsers as reader-macros (not the normal kind of macro). The first parser parses PEG syntax and creates an esrap program. That esrap program, bound as a reader-macro, reads Prolog syntax and returns a bunch of lisp forms to the reader. I have a file of code that contains both, lisp and Prolog syntax (cl-heredoc to switch between the syntaxes), e.g. https://github.com/guitarvydas/paraphrase/blob/master/prolog.lisp The parsers read characters, not forms. (lisp) #{ prolog(A,B,c) :- p1(A), p2(B,c). } (morelisp) I am making at least 2 assumptions: 1. That using different name spaces for the various parsers will help me preserve my sanity, (regression testing the PEG parser using itself brings me to the limits of my comprehension :-), 2. That a reader macro must return a single form. I actually want to return a separate 'defun' for every prolog rule in the file. (Writing this, just now, makes me ask myself why I don't just put #{ ... } around every separate rule...) (I even started fooling around with a Python syntax). This line of thinking was inspired by the Gambit Scheme talk at ILC2010, where they showed inline infix mathematical expressions. Thanks for your suggestions. pt

4 3

Wild pathnames
by Faré 18 Mar '14

18 Mar '14

Is there a mailing-list where to report such issues, and where to contact vendors so they fix their bugs? mkdir -p /tmp/x ; touch "/tmp/x/" ; for i in sbcl ccl clisp cmucl ecl abcl scl allegro lispworks gcl xcl ; do echo $i ; cl -l $i -iw '(let ((x (directory "/tmp/x/"))) (list "'$i'" x (pathname-name (first x))))' ; done #cl Escape properly: ("sbcl" (#P"/tmp/x/\\") "") ("cmucl" (#P"/tmp/x/\\") "") ("ccl" (#P"/tmp/x/\\") "\\") ("lispworks" (#P"/tmp/x/\\") "\\") ("scl" (#P"file://localhost/tmp/x/") "") Read badly: ("clisp" (#P"/tmp/x/*") :WILD) ("ecl" (#P"/tmp/x/*") :WILD) ("allegro" (#P"/tmp/x/*") :WILD) ("xcl" (#P"/tmp/x/*") :WILD) Error out: abcl Fatal condition: Bad place for a wild pathname. gcl: Fatal condition: Condition in LET [or a callee]: INTERNAL-SIMPLE-FILE-ERROR: File error on "/tmp/x/": File "/tmp/x/" is wild —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org It ain't what a man don't know that makes him a fool; it's the things he knows that ain't so. — Josh Billings

3 3

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