parenscript-devel

parenscript-devel@common-lisp.net

373 discussions

[parenscript-devel] Inconsistent treatment of keyword symbols
by Daniel Gackle 10 Oct '07

10 Oct '07

This works: (ps (defvar :x 1)) => "var x = 1;" and so does this: (ps x) => "x;" but this doesn't: (ps :x) Attached is a simple patch to make this work for keywords. Is there any reason not to do this? Daniel

2 1

[parenscript-devel] &whole behaves differently in PS
by Daniel Gackle 23 Sep '07

23 Sep '07

I'm writing some unit tests for PS functions and want to be able to report the test expressions that fail. &whole is perfect for this. But it doesn't quite behave as expected. In Lisp: (defmacro lisp-blah (x y &whole w) w) (macroexpand-1 '(lisp-blah 10 20)) => (LISP-BLAH 10 20) In Parenscript: (defpsmacro ps-blah (x y &whole w) w) (ps::ps-macroexpand '(ps-blah 10 20)) => (10 20) Also, if you do this: (defmacro/ps blah (x y &whole w) w) then the following expression hangs: (ps::ps-macroexpand '(blah10 20)) Daniel

2 2

[parenscript-devel] Need a meaningful error message when PS macro references unbound var
by Daniel Gackle 20 Sep '07

20 Sep '07

When a macroexpansion tries to evaluate an unbound variable, as in the following, (ps (macrolet ((blah () x)) (blah))) the resulting error message is unhelpful: "Attempt to take the car of "Unbound Value" which is not listp." Could it say "Attempt to take the value of the unbound variable X" instead? Daniel

2 1

[parenscript-devel] Bug: inconsistent expansion of local macro
by Daniel Gackle 20 Sep '07

20 Sep '07

When a macro like this: (defpsmacro blah (x) 'xyz) ... is shadowed by a local macro like this: (ps (defun test1 () (macrolet ((blah (x) `(aref data ,x))) (when (blah x) (setf (blah x) 123))))) ... it's possible to get an inconsistent macroexpansion: => "function test1() { if (data[x]) { xyz = 123; }; }; Daniel

2 1

[parenscript-devel] Symbol-macrolet bug
by Daniel Gackle 20 Sep '07

20 Sep '07

This works correctly: (ps (symbol-macrolet ((blah "y")) (setf (aref x blah) 123))) => "x['y'] = 123;" ... while it appears this does not: (ps (symbol-macrolet ((blah "y")) (setf (@ x blah) 123))) => "x.blah = 123;" Daniel

2 1

[parenscript-devel] Macroexpand doesn't work
by Daniel Gackle 13 Sep '07

13 Sep '07

(defpsmacro blah () 123) => NIL (ps (blah)) => "123;" but: (ps::macroexpand-1 '(blah)) => (BLAH) Wouldn't one expect this to provide the macroexpansion? I can't find anything in Parenscript now corresponding to expand-form or whatever it used to be called. Daniel p.s. I wrote "123;" above for neatness, but PS actually emits "123;\n". Seems the newline should only be there when more than one line of JS is generated. It's a minor point, but noticeable when working from the REPL.

2 2

[parenscript-devel] New ParenScript release.
by Vladimir Sedach 29 Aug '07

29 Aug '07

Hello everyone, I've just put up the tarball and documentation for the new ParenScript release. It features a rewrite of the compiler and JavaScript printer, along with many user-visible changes, the most notable being the addition of setf places (defsetf and defun setf), and Red Daly's excellent contribution of Common Lisp-like lambda lists for ParenScript functions (we now have &optional, &rest and &key). Due to the rewrite of the printer, JavaScript generation has gotten a major speed boost. As well, I've updated the tutorial and ensured it worked correctly with the latest AllegroServe (the tutorial PDF will be going away in the next release - I plan to put it up on Cliki where it can be updated in a more timely manner). Happy hacking, Vladimir

1 0

[parenscript-devel] Trial period for new ParenScript release.
by Vladimir Sedach 24 Aug '07

24 Aug '07

Hello everybody, I've just finished committing the last of my planned changes to the ParenScript documentation to reflect the new updates that have been done since the last release. I plan to make the next release available on Tuesday, August 28th. Until then, I invite everybody to go over the darcs repository version of ParenScript and report any problems that you may find. Thank you, Vladimir Sedach

1 0

[parenscript-devel] BUG: cond doesn't generate expressions.
by Vladimir Sedach 23 Aug '07

23 Aug '07

This bug comes up if you try to do something like (return (cond... A quick workaround to this problem if you're using SBCL or Allegro is to (import-macros-from-lisp 'cond), since their cond works by expanding into nested if forms (this is what we use in our ParenScript application, which is why this bug slipped through the cracks for so long). The nested-if approach is also how I'm going to fix this problem and generate cond-expressions (yeah, this is another one of those bug reports that I use as a to-do). Happy hacking, Vladimir

1 1

[parenscript-devel] lisp-like lambda lists (keyword, option, and rest arguments)
by Red Daly 15 Aug '07

15 Aug '07

In my local version I have added support for very Lispy lambda lists with keyword, optional, and &rest arguments. Is this a feature we should add to the language? The Javascript convention for passing named arguments is to have an options variable that functions as a hash table for keywords. I use this convention for passing keyword arguments in Parenscript. Also, when a quoted symbol (e.g. a keyword) is found in a function call, the an options object is constructed. Here are a few examples (defun name (first last &key (prefix "Ms.") (middle "")) (return (+ prefix " " first " " middle " " last))) => function name (first last options) { options.prefix = options.prefix === undefined ? "Ms." : options.prefix; options.middle = options.middle === undefined ? " " : options.middle; return prefix + " " + first " " + middle + " " + last; } (defun vote (&optional (times 1)) ...) => function vote (times) { times = times === undefined ? 1 : times; ...} (defun append (&rest lists) ...) => function append() { lists = arguments.slice(0); ...} (name "John" "Cunningham" :prefix "Mr." :middle "Appleton") => name("John", "Cunningham", { prefix : "Mr." , middle : "Appleton" }) I like having the extra lambda list features available in my own code. Should we add this to Parenscript? -Red

3 4

← Newer
1
...
30
31
32
33
34
35
36
37
38
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

parenscript-devel