parenscript-devel September 2011

parenscript-devel@common-lisp.net

5 participants
8 discussions

[parenscript-devel] [PATCH] Implementation of TRY-EXPRESSIONIZE-IF? that doesn't call the printer.
by sblist＠me.com 17 Dec '11

17 Dec '11

I needed to avoid secondary calls to the printer for the purpose of generating source mappings, but this seems like a more precise definition anyway (unless I've missed something). Scott --- src/special-operators.lisp | 14 ++++++++++---- 1 files changed, 10 insertions(+), 4 deletions(-) diff --git a/src/special-operators.lisp b/src/special-operators.lisp index 3a77ae5..be95a5f 100644 --- a/src/special-operators.lisp +++ b/src/special-operators.lisp @@ -130,10 +130,16 @@ `(ps-js:label ,name ,(wrap-block-for-dynamic-return name (compile-statement `(progn ,@body)))))) (defun try-expressionize-if? (form) - (< (count #\Newline (with-output-to-string (*psw-stream*) - (let ((*ps-print-pretty* t)) - (parenscript-print (compile-statement form) t)))) - (if (= (length form) 4) 5 4))) + (destructuring-bind (if condition + (block . consequent) + &optional + else + alternative-block) + (compile-statement form) + (declare (ignore if condition else block)) + (and (= (length consequent) 1) + (or (null alternative-block) + (= (length alternative-block) 2))))) (define-statement-operator return-from (tag &optional result) (if (not tag) -- 1.7.6

2 2

[parenscript-devel] Bug: RETURN-FROM inside a lambda doesn't return anything
by Daniel Gackle 12 Dec '11

12 Dec '11

I thought this was working at some point, but it doesn't seem to now. FOO() returns undefined in JS, when it should return 123: (defun bar (fn) (funcall fn)) (defun foo () (bar (lambda () (return-from foo 123)))) It seems the value stored under the name "ps-return-value" isn't actually returned: function foo() { try { return bar(function () { throw { 'ps-block-tag' : 'foo', 'ps-return-value' : 123 }; }); } catch (err) { if (err && 'foo' === err['ps-block-tag']) { err['ps-return-value']; } else { throw err; }; }; };

2 3

[parenscript-devel] BLOCK/RETURN-FROM
by sblist＠me.com 12 Dec '11

12 Dec '11

Hi, I was wondering if the BLOCK/RETURN-FROM feature in PS intends to support the following case: (ps (defun foo () (flet ((bar () (return-from foo 42))) (bar)))) => WARNING: Returning from unknown block FOO "function foo() { var bar = function () { return 42; }; return bar(); };" In order to try and get around the warning, I tried this: (ps (defun baz () (block foo (flet ((bar () (return-from foo 42))) (bar))))) => WARNING: Returning from unknown block FOO "function baz() { var bar = function () { return 42; }; return bar(); };" but that didn't seem to work. Any ideas on how to achieve lexical return here? - Scott

4 4

Re: [parenscript-devel] what's wrong?
by F D 12 Dec '11

12 Dec '11

Yes it helps. Many Thanks, I made a mistake and forgot to use a (lambda...) Is there something that can help to convert js code to parenscript code? FD

3 3

[parenscript-devel] [PATCH] Eliminate STYLE-WARNINGs during compilation
by sblist＠me.com 13 Sep '11

13 Sep '11

The following patch should eliminate these two compilation STYLE-WARNINGs: STYLE-WARNING: Overwriting already existing readtable #<NAMED-READTABLE :PARENSCRIPT {10030FA571}>. style-warning: Implicitly creating new generic function ps-print. Scott --- src/package.lisp | 7 ++++--- src/printer.lisp | 1 + 2 files changed, 5 insertions(+), 3 deletions(-) diff --git a/src/package.lisp b/src/package.lisp index c2c6eb2..be504da 100644 --- a/src/package.lisp +++ b/src/package.lisp @@ -3,9 +3,10 @@ (pushnew :parenscript *features*) (eval-when (:compile-toplevel :load-toplevel :execute) - (named-readtables:defreadtable :parenscript - (:merge :standard) - (:case :invert))) + (unless (named-readtables:find-readtable :parenscript) + (named-readtables:defreadtable :parenscript + (:merge :standard) + (:case :invert)))) (named-readtables:in-readtable :parenscript) diff --git a/src/printer.lisp b/src/printer.lisp index 43d6f57..da6bae5 100644 --- a/src/printer.lisp +++ b/src/printer.lisp @@ -44,6 +44,7 @@ vice-versa.") (cons (get-output-stream-string *psw-stream*) %psw-accumulator)))))))) +(defgeneric ps-print (form)) (defgeneric ps-print% (js-primitive args)) (defmacro defprinter (js-primitive args &body body) -- 1.7.6

2 1

[parenscript-devel] Lexical scoping with LAMBDA
by sblist＠me.com 13 Sep '11

13 Sep '11

It appears as though there might be a gap in the lexical scoping implementation in the compiler: (ps (lambda (x) (let ((x 1)) (foo x)) (incf x))) => "function (x) { var x = 1; foo(x); return ++x; };" vs. (ps (let ((x 10)) (let ((x 1)) (foo x)) (incf x))) "var x = 10; var x33 = 1; foo(x33); ++x;" Although function parameters have their own lexical bindings, the environment still needs to be informed of those bindings so that LET forms in the function body can rename any conflicts. Scott

4 5

[parenscript-devel] Commit abf27a29f introduces bug in / operator
by sblist＠me.com 06 Sep '11

06 Sep '11

(ps (floor (1- x) y)) => Error: There is no applicable method for the generic function #<STANDARD-GENERIC-FUNCTION PARENSCRIPT::PS-PRINT% (66)> when called with arguments (1- (PARENSCRIPT::X)) This bug isn't present in abf27a29f's parent. Scott

2 1

[parenscript-devel] question about dolist
by Canhua 05 Sep '11

05 Sep '11

hi, I found that the following compiles to an error, I wonder if this is a bug or there is something I misunderstand. (ps (setf v (let ((x 0)) (dolist (i '(1 2 3)) (incf x i)) x))) where the error is: The Parenscript form (for (i (#1=_js_arrvar467 '(1 2 3)) (#2=_js_idx466 0)) ((not (>= #2# #))) ((setf #2# #)) (setq i (aref #1# #2#)) (incf x i)) cannot be compiled into an expression. [Condition of type compile-expression-error] Hope you help me, thank you.

2 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

parenscript-devel September 2011