parenscript-devel

parenscript-devel@common-lisp.net

373 discussions

[parenscript-devel] Fwd: test failure on Allegro
by Anton Vodonosov 07 Jan '12

07 Jan '12

-------- Forwarding the Robert's response -------- 06.01.2012, 19:06, "Robert Goldman" <rpgoldman(a)sift.info>: On 1/6/12 Jan 6 -8:51 AM, Anton Vodonosov wrote: > I don't know, the test results for Allegro are contributed by > Robert Goldman, lets ask him. > > Robert, when you run tests do you use alisp or mlisp? I use alisp (ANSI-compliant) lisp exclusively for these tests. Cheers, r P.S. You may need to forward this, since I am not a subscriber of the parenscript mailing list. > 06.01.2012, 17:13, "Gary King" <gwking(a)metabang.com>: >> Hi Anton, >> >> Is this mlisp or alisp? If the former, it's almost surely a case-sensitivity issue. >> >> thanks, >> >> On Jan 6, 2012, at 2:57 AM, Anton Vodonosov wrote: >>> As you may see, parenscript fails on Allegro: >>> >>> ; While compiling (:TOP-LEVEL-FORM "package.lisp" 54) in /home/rpg/lisp/cl-test-grid/quicklisp/dists/quicklisp/software/parenscript-2.3/src/package.lisp: >>> Unhandled ERROR is signaled: There is no readtable named :PARENSCRIPT.

2 2

[parenscript-devel] Function application and variable renaming
by Scott Bell 07 Jan '12

07 Jan '12

PS appears not to support Lisp-1-style function application in the presence of variable renaming: (ps (let ((a 10)) (let ((a (lambda () 17))) (a)))) => "(function () { var a = 10; var a1 = function () { return 17; }; return a(); })();" If I use FUNCALL, or even FLET instead of LET, the correct code is generated. There's obviously some Lisp-2 action going on in PS, but unless I'm mistaken it seems like both forms can be supported. Scott

2 1

[parenscript-devel] test failure on Allegro
by Anton Vodonosov 06 Jan '12

06 Jan '12

Hello. I am running the tests of some CL libraries, including parenscript. You may find the results here: http://common-lisp.net/project/cl-test-grid/pivot_lib_ql-lisp.html. The OK/FAIL links refer to the library test logs with the failure details. As you may see, parenscript fails on Allegro: ; While compiling (:TOP-LEVEL-FORM "package.lisp" 54) in /home/rpg/lisp/cl-test-grid/quicklisp/dists/quicklisp/software/parenscript-2.3/src/package.lisp: Unhandled ERROR is signaled: There is no readtable named :PARENSCRIPT. Best regards, - Anton

2 2

[parenscript-devel] Bug: JS contains inappropriate "funcall" in SBCL
by Daniel Gackle 26 Dec '11

26 Dec '11

In SBCL, PS generates "funcall(bar)" below instead of "bar()". In CCL, it's fine. Daniel (ps (defun foo () (flet ((blah () (return-from foo (bar))))))) => function foo() { try { var blah = function () { throw { 'ps-block-tag' : 'foo', 'ps-return-value' : funcall(bar) }; }; return null; } catch (err) { if (err && 'foo' === err['ps-block-tag']) { return err['ps-return-value']; } else { throw err; }; }; };

3 2

[parenscript-devel] Upcoming Parenscript release
by Vladimir Sedach 21 Dec '11

21 Dec '11

Hello, I'm planning on a new Parenscript release shortly after the new year. There are a lot of bugfixes and other functionality changes that have gone in since the last release. Feel free to try out the new PS from the repository (git clone http://common-lisp.net/project/parenscript/git/parenscript) and report any problems or bugs you find. Happy hacking, Vladimir

1 0

[parenscript-devel] bug: RETURN-FROM doesn't work with LABELS
by Daniel Gackle 17 Dec '11

17 Dec '11

This produces incorrect code (a throw with no corresponding catch): (defun foo () (labels ((bar (x) (when (evenp x) (return-from bar "even")) (blah x))) (bar 9))) If you change LABELS to FLET then it works. Daniel

2 1

[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] "let over lambda" seems buggy
by Canhua 17 Dec '11

17 Dec '11

hi, all, I found that (create "fn" (let ((x)) (lambda () x))) compiles to { 'fn' : (x = null, function () { return x; }) } wherein the variable x may conflict with a variable with the same name outside this code. How may avoid this? How may I achieve "let over lambda" closure effect as in common lisp? Thanks.

3 7

[parenscript-devel] Today's bug fixes
by Daniel Gackle 13 Dec '11

13 Dec '11

Thanks for the batch of bug fixes. We've upgraded to the latest commit. The only difference I saw in our compiled JS was more parentheses around operators. By inspection, they looked correct. I'm not sure the compiler needs to do this, but it's a minor point: (new Date()).getTime(); Also, I was getting a compiler warning for an unused variable in printer.lisp, so I committed an ignore for it. Daniel

1 0

[parenscript-devel] Bug: cases where PS generates syntax errors instead of expressions
by Daniel Gackle 12 Dec '11

12 Dec '11

(ps (create a 11 b 22)) => "{ a : 11, b : 22 };", which is illegal at the top level because JS interprets the curly braces as statement block delimiters. PS should probably generate "({ a : 11, b : 22 })" instead. Similarly, (ps (lambda () 123)) => "function () { return 123; };" is also illegal at the top level and should also be wrapped in parens. Such forms obviously don't come up much in source files, but they do in a REPL. We're making a PS REPL (and source-level debugger) for Emacs, which is how we ran across them.

2 1

← Newer
1
...
8
9
10
11
12
13
14
...
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