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

[parenscript-devel] Scoping bug with lambdas
by sblist＠me.com 01 Mar '11

01 Mar '11

Hi, Here's the misbehaviour: (ps (let ((x 5)) (let ((x 7)) (funcall (lambda (x) (+ x 9)) x)))) => "var x = 5; var x51 = 7; (function (x) { return x51 + 9; })(x51);" Obviously the X inside the lambda body can remain just plain X since it is bound in a new scope. Scott

2 1

[parenscript-devel] Parenscript questions
by Miron Brezuleanu 23 Feb '11

23 Feb '11

Hi, I'm a Common Lisp newbie playing with Parenscript and WebGL. The source of 'http://learningwebgl.com/lessons/lesson01/index.html' contains a very simple example, with identifiers like gl.LEQUAL or gl.ARRAY_BUFFER. I can't figure out how to write those in Parenscript. I read the Symbol Conversion section of the manual ('http://common-lisp.net/project/parenscript/reference.html#section-symbolconv') but couldn't figure out what syntax to use. I ended up trying with a bigger hammer and modifying function encode-js-identifier in utils.lisp. That allowed me to write gl.*lequal* and get gl.LEQUAL. Is there a way to write these symbols without patching Parenscript? (BTW, modified function at 'https://gist.github.com/841088'). Many thanks, -- Miron Brezuleanu

3 2

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

09 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 03 Feb '11

03 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 03 Feb '11

03 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