April 2009 - parenscript-devel - mailman3.common-lisp.net

[parenscript-devel] ps-compile-file and eval-when, patch included
by Red Daly 29 Apr '09

29 Apr '09

I have had Parenscript file compilation working in a local version of Parenscript for a long time, but this feature is still missing from the official Parenscript. It seems like a logical feature to place into the main Parenscript project. Parenscript is useful for creating large Javascript applications and where there are large software projects there is a need for files. Some Parenscript interacts with Lisp code, but other Parenscript is written purely for the front-end. This sort of code belongs in a standalone Parenscript file. A naiive file compiler for Parenscript looks like this: (defun ps-compile-file (source-file) (with-open-file (input source-file :direction :input) (let ((end-read-form '#:unique)) (flet ((read-form () (read input nil end-read-form))) (do ((form (read-form) (read-form)) (forms nil)) ((eql form end-read-form) (ps:ps* `(progn ,@(nreverse forms))))))) However, just as in Lisp, it is helpful to have a little more control when compiling files than just creating a PROGN with the form and compiling as if it were any other code. It is useful to have EVAL-WHEN forms to manipulate the reader and so on. Therefore I have added the idea of top-level forms, including the EVAL-WHEN special form, to address this issue. EVAL-WHEN in Parenscript is similar to EVAL-WHEN in lisp but it takes into account the fact that when compiling the relevant language is LISP, but when executing the relevant language is Parenscript. An example of using EVAL-WHEN to define an IN-PACKAGE macro to manipulate the reader: (defpsmacro in-package (package-designator) `(eval-when (:compile-toplevel) (setf cl:*package* (find-package ,package-designator)))) Attached is a patch against the current git repository with this change and another bug fix. Best regards, Red

2 1

[parenscript-devel] Bug in composed conditional expressions
by Daniel Gackle 29 Apr '09

29 Apr '09

I'm seeing a bug in how conditionals are grouped together. (ps (return (if (if x y z) a b))) => "return x ? y : z ? a : b;" This requires parentheses in order to evaluate the way the PS expression was clearly intended, namely: (x ? y : z) ? a : b PS appears to make the wrong decision about when to include parentheses, since it does it here when the default would do: (ps (return (if x y (if z a b)))) => "return x ? y : (z ? a : b);" Daniel

2 1

[parenscript-devel] Keyword arguments and quoted symbols in Parenscript
by Red Daly 29 Apr '09

29 Apr '09

Hello ParenScripters, I have modified the behavior of keywords found in Parenscript source to be parsed into (PS-QUOTE keyword) instead of (JS-VARIABLE keyword). This seems to make more sense because in Lisp, evaluating a keyword yields the keyword itself rather than the value bound to it. As a result, the ability to paass keyword arguments to functions is now restored. CL-USER> (ps:ps (foo "bar" :quix "quo" :etc "etc...")) "foo('bar', { quix : 'quo', etc : 'etc...' });" Whereas this used to yield foo('bar', quix, 'quo', etc, 'etc...') In general, symbols occupy a strange place in Parenscript. Javascript has no analogue of Lisp symbols, so there is no sensible translation of symbols that works for everyone. Nonetheless, quoted symbols are used in many Parenscript macros to fake having real symbols in javascript. We could build in the ability to translate symbols to some javascript form, e.g. (ps:ps (make-instance 'animal)) => makeInstance( symbolTable["ANIMAL"] ) The latter part of this post is just food for thought. I will go ahead and commit the patch for the former part of this post unless someone objects. Red

3 5

[parenscript-devel] Minor patch: inconsistent function name
by Daniel Gackle 21 Apr '09

21 Apr '09

Unless I'm missing something, the same function was still being referred to with names COMPLEX-JS-EXPR? and COMPLEX-JS-EXPR-P. Below is a patch to use the first name consistently. Daniel >From 6e7190ace745f5bb2448249b368104a9a8917679 Mon Sep 17 00:00:00 2001 From: Daniel Gackle <danielgackle(a)gmail.com> Date: Mon, 20 Apr 2009 16:14:20 -0700 Subject: [PATCH] Use the name of function COMPLEX-JS-EXPR? consistently. --- src/lib/ps-loop.lisp | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/src/lib/ps-loop.lisp b/src/lib/ps-loop.lisp index 7eeae46..e806e41 100644 --- a/src/lib/ps-loop.lisp +++ b/src/lib/ps-loop.lisp @@ -1,6 +1,6 @@ (in-package :parenscript) -(defun complex-js-expr-p (expr) +(defun complex-js-expr? (expr) (if (symbolp expr) (find #\. (symbol-name expr)) (consp expr))) @@ -26,7 +26,7 @@ destructurings body) (macrolet ((with-local-var ((name expr) &body body) (once-only (expr) - `(let ((,name (aif (and (complex-js-expr-p ,expr) (ps-gensym)) + `(let ((,name (aif (and (complex-js-expr? ,expr) (ps-gensym)) (progn (push (list 'var it ,expr) prologue) it) ,expr))) -- 1.6.1

2 2

[parenscript-devel] ELS 2009 in Milan, Italy: Call for Participation
by Marco Antoniotti 15 Apr '09

15 Apr '09

Apologies for multiple postings.... ************************************************************************ 2nd European Lisp Symposium (ELS 2009) Milan, Italy, May 27-29, 2009 Universita` degli Studi di Milano-Bicocca www.european-lisp-symposium.org ************************************************************************ CALL FOR PARTECIPATION ********************** REGISTRATION IS NOW OPEN AT www.european-lisp-symposium.org. Take advantage of the early bird registration fee. Scope and Program Highlights: ***************************** The purpose of the European Lisp Symposium is to provide a forum for the discussion of all aspects of the design, implementation and application of any of the Lisp dialects. We encourage everyone interested in Lisp to participate. The European Lisp Symposium 2009 program includes presentations of high quality papers about novel research results, insights and lessons learned from practical applications, and educational perspectives, all involving Lisp dialects, including Common Lisp, Scheme, Emacs Lisp, AutoLisp, ISLISP, Dylan, Clojure, and so on. Kent Pitman will give the keynote address on Thursday, May 28. The presentations will be divided into two categories. * Original contributions. * Work in progress describing ongoing work that will be discussed in the form of a "writers' workshop". The writers' workshops will take place at the symposium in Milan on May 28, 2008. Social Events: ************** Friday 29th evening, Conference Banquet Saturday 30th morning, Guided tour to the "Futurismo" Exhibit in the center of Milan; 2009 marks the 100th anniversary of the Futurism Manifesto; stretching it, the harbinger of Lisp 50 years later. Program Chair: ************** * Antonio Leitao, Technical University of Lisbon, Portugal Local Chair: ************ * Marco Antoniotti, DISCo, Universita`† Milano Bicocca, Italy Program committee: ****************** * Giuseppe Attardi, Universita`† di Pisa , Italy * Pascal Costanza, Vrije Universiteit Brussel, Belgium * Irene Durand, Universite` Bordeaux 1, France * Marc Feeley, Universit` de Montreal, Canada * Ron Garret, Amalgamated Widgets Unlimited, USA * Gregor Kiczales, University of British Columbia, Canada * Scott McKay, ITA Software, Inc., USA * Peter Norvig, Google Inc., USA * Julian Padget, University of Bath, UK * Kent Pitman, PTC, USA * Christian Queinnec, Universite` Pierre et Marie Curie, France * Christophe Rhodes, Goldsmiths College, University of London, UK * Robert Strandh, Universite` Bordeaux 1, France * Mark Tarver, Lambda Associates, UK * Didier Verna, EPITA Research and Development Laboratory, France * JonL White, TheGingerIceCreamFactory of Palo Alto, USA * Taiichi Yuasa, Kyoto University, Japan Registration Fees: ****************** * Early registration before April 25, 2008: Students EU60, regular EU120. * Late registration before May 16, 2008: Students EU80, regular EU160. * Onsite registration: Students EU100, regular EU220. Registration will include the proceedings, coffee breaks, the symposium dinner and other amenities. Accommodation is not included.

1 0

[parenscript-devel] New goodies in the repository thanks to Daniel Gackle and Scott Bell
by Vladimir Sedach 12 Apr '09

12 Apr '09

Hello, There's some neat new stuff, including partial implementations of 'loop' and 'destructuring-bind', that have been sent in by Daniel Gackle and Scott Bell. Check it out. I'm also busy rewriting the intermediate representation of Parenscript to look like a 1-1 representation of JavaScript in s-exp format. The eventual goal will be to standardize this representation, and move the printing facility into a new project, tentatively entitled "The JS Toolkit," which will use the standardized notation to provide parsing and printing for textual JavaScript, and later a JavaScript compiler entirely in Common Lisp, to provide Parenscript with better unit testing tools and for letting you have server-side JavaScript in your own web applications (as well as being useful for other CL projects). Thank you, Vladimir

1 0