parenscript-devel September 2007

parenscript-devel@common-lisp.net

2 participants
7 discussions

Start a nNew thread

[parenscript-devel] Bug: nested symbol-macrolet
by Daniel Gackle 11 Oct '07

11 Oct '07

This works in CL: (symbol-macrolet ((x 123) (y (* 2 x))) y) => 246 ... but produces an error in PS. Seems wrong? Dan

2 1

[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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

parenscript-devel September 2007