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

[parenscript-devel] Cool package hack
by Vladimir Sedach 08 Feb '11

08 Feb '11

I came across this post recently: http://e-arrows.sakura.ne.jp/2011/01/cl-wrapper-for-google-closure.html It uses an empty package and *debugger-hook* to generate Parenscript forms without having to refer to PS or PS*, and to fake the "." symbol property accessors for JS libraries that use objects as namespaces. Vladimir

1 0

[parenscript-devel] Parenscript 2.3 coming soon
by Vladimir Sedach 02 Feb '11

02 Feb '11

Hi everybody, I want to make a new release of Parenscript soon. It would be cool if you could test out the repository version (http://common-lisp.net/project/parenscript/git/parenscript) and see if it works with your code. Happy hacking, Vladimir

1 0

[parenscript-devel] Another CASE fall-through bug
by Daniel Gackle 02 Feb '11

02 Feb '11

The recent bug fixes seem to have worked (thanks). It seems I can't remove my warning-silencing workaround code, though (hacking *defined-operators*). I mention this because it's not clear to me if the intention was to not need that workaround anymore. What should the current behavior be - you get a warning if you redefine a built-in operator, but not an error? I did encounter a new problem while removing other workarounds. At least I think it's a new problem rather than a failure to fix the related earlier bug - I'm not really sure. This incorrectly falls through to the 456 case when foo1() returns true and foo2() does not. The example can probably be pared down further, but I don't have time to make it shorter. (defun blah (x) (case x (123 (cond ((foo1) (when (foo2) (when (foo3) (return-from blah nil)) t)))) (456 (foo7)))) function blah(x) { switch (x) { case 123: if (foo1()) { if (foo2()) { if (foo3()) { return null; }; return true; }; }; case 456: return foo7(); }; };

2 1

[parenscript-devel] How to use an external JavaScript library (or framework)?
by nitralime 02 Feb '11

02 Feb '11

Hi folks! I'm almost sure that these questions have been already asked. However, I couldn't find any search utility in the archive of this mailing list and hence ask them again: How can an external JavaScript library be used in Parenscript? Which JavaScript library does suit Parenscript well? What is the idomatic way to integrate a JavaScript library into an application using Parenscript? Any answer (resp. pointer) is very much appreciated. Regards Nik

3 3

[parenscript-devel] An operator precedence error
by Daniel Gackle 30 Jan '11

30 Jan '11

(unless (equal (= 3 3) (= 3 4)) (foo)) generates this, which is wrong, since FOO should be called: if (3 === 3 != 3 === 4) { foo(); }; I think more parentheses are needed. Daniel

2 1

[parenscript-devel] Syntax error assigning compound expression in object literal
by Daniel Gackle 30 Jan '11

30 Jan '11

The generated JS is invalid here, somewhat unexpectedly (I suppose parentheses are required): (defun foo (obj) (create :abc (let ((x (gethash "blah" obj))) (if x 123 456)))) => function foo(obj) { var x; return { 'abc' : x = obj['blah'], x ? 123 : 456 }; };

2 1

[parenscript-devel] Why is there a WITH clause in my loop?
by Daniel Gackle 30 Jan '11

30 Jan '11

Here's a really strange one. We have a form like the following. I've stripped it down for brevity, so it looks weird: (loop :for time :from time1 :below time2 :do (when (foo (λ () (bar (λ () (blah)) time)) time) (break))) It used to generate this: for (var time = time1; time < time2; time += 1) { if (foo(function () { return barr(function () { return blah(); }, time); }, time)) { break; }; }; But now it generates this: for (var time = time1; time < time2; time += 1) { with ({ time : time }) { if (foo(function () { return bar(function () { return blah(); }, time); }, time)) { break; }; }; }; That is one weird WITH clause in there! No doubt it has something to do with lexical scoping magic going on under the hood. But I definitely don't want it in a performance-critical loop. Daniel

5 8

[parenscript-devel] FLET, LABELS, and MULTIPLE-VALUE-BIND are broken
by Daniel Gackle 30 Jan '11

30 Jan '11

I've attempted to upgrade again to the latest PS. It looks like the issues we discussed last month are fixed (thank you), but there are some serious new breakages: 1. FLET and LABELS no longer accept &OPTIONAL, &REST, or &KEY arguments 2. MULTIPLE-VALUE-BIND doesn't work: in the JS for (PS (MULTIPLE-VALUE-BIND (A B) (BLAH) (+ A B))), the function BLAH doesn't appear. I'll post if I notice anything else.

2 3

[parenscript-devel] PS warning being treated as error by ASDF+SBCL
by Daniel Gackle 26 Jan '11

26 Jan '11

PS does the following to warn you about redefining built-in operators: (warn "Redefining Parenscript operator/macro ~A" name) As it happens, we redefine DEFMACRO and IN-PACKAGE to expand to nothing and @ to expand to something a bit different than what PS does. The purpose of these redefinitions is to support cross-compiling a number of files to both CL and JS. Unfortunately, that warning turns into an error preventing ASDF from loading the system in SBCL: ; compilation unit aborted ; caught 1 fatal ERROR condition ; caught 3 WARNING conditions I don't see what the ERROR is, since only the above three warnings are written to the REPL. It goes away, however, when I comment out the WARN form above. I have an ugly workaround for this (reach in to PS::*PS-DEFINED-OPERATORS* and rip out these three symbols before attempting to redefine them), but that seems like a horrible thing to do. Resorting to SBCL's condition-muffling mechanism seems even worse. Just to be clear, I don't object to PS issuing the warning, just to the fact that it turns into a fatal error along the way. So I guess my question is: what's the intended way to redefine a PS operator/macro, on the rare occasion when one really does need to do that? Daniel

3 4

[parenscript-devel] CASE is still broken with RETURN
by Daniel Gackle 17 Jan '11

17 Jan '11

This generates an incorrect fall-through when A is "a" and FOO returns NIL: (defun blah (a) (case a ("a" (when (foo) (return-from blah 111))) ("b" t))) Note that if you replace WHEN with IF, it works.

2 1