August 2011 - parenscript-devel - mailman3.common-lisp.net

[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] 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] Division operator broken on cons arguments
by Daniel Gackle 29 Aug '11

29 Aug '11

In commit abf27a2, (ps (/ (foo) (bar))) => There is no applicable method for the generic function: #<STANDARD-GENERIC-FUNCTION PS-PRINT% #x302001032B2F> when called with arguments: (FOO NIL) [Condition of type SIMPLE-ERROR]

1 0

[parenscript-devel] with-slots inconsistence
by Canhua 28 Aug '11

28 Aug '11

hi, I find that (with-slots (a b) this (a)) compiles to a(), rather than this.a(), as I would expected. Which one is what you expected?

2 3

[parenscript-devel] question about WHO-PS-HTML syntax
by Canhua 26 Aug '11

26 Aug '11

hi, what's the parenscript WHO-PS-HTML syntax of this html snippet: <p>t0<span>t1</span></p> I tried (who-ps-html (:p "t0" (:span "t1"))), which evals to an error, saying function :span is not defined. Althrough I also found that CL-WHO accepts the following: (who:with-html-output-to-string (s) (:p "t0" (:span "t1"))) Thanks.

2 2

[parenscript-devel] Parenscript 2.3 compilation problem
by Erik Huelsmann 25 Aug '11

25 Aug '11

Hi, This week, Alessio Stalla and I are trying to get Parenscript to compile on ABCL. We're using Parenscript 2.3 as distributed with Quicklisp. Parenscript 2.2 worked fine, after fixing a potential readtables issue. However, Parenscript 2.3 fails compilation during the compilation of the (DEFINE-EXPRESSION-OPERATOR LET # ...) toplevel form. The problem is that it generates an expression (VAR X), which is then expanded to (DEFPARAMETER X). However, that's non-conforming because the initial value is required according to the CLHS. Looking at the definition of the VAR macro, I see the problem: (defmacro VAR (name &optional value docstring) `(defparameter ,name ,@(when value (list value)) ...)) can indeed lead to a (DEFPAMETER X) I haven't found out if/why this isn't a problem on Parenscript 2.2 or why Parenscript 2.3 would cleanly compile on SBCL, because - like ABCL - it rejects forms like that. If it is ABCL that's broken here, could you help us fix it? If not, could you fix parenscript to work on ABCL? I'm eager to learn about your analysis of the situation. If you need help on settin up ABCL, I'll gladly provide it. Bye, Erik

2 2