parenscript-devel May 2011

parenscript-devel@common-lisp.net

4 participants
4 discussions

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] Possible bug in Parenscript 2.3 (*ps-lisp-library*)
by TeMPOraL 19 Jun '11

19 Jun '11

Hi, I am working on CCL and I have migrated from Parenscript 2.2 to 2.3, and now I get warnings (pasted below) when including Parenscript runtime library (*ps-lisp-library*). Generated Javascript has bugs; in particular, 'member' function always returns false. WARNING: CL-USER> (parenscript:ps* parenscript:*ps-lisp-library*) ; Warning: Returning from unknown block nilBlock ; While executing: PARENSCRIPT::RETURN-EXP, in process repl-thread(9). ; Warning: Returning from unknown block nilBlock ; While executing: PARENSCRIPT::RETURN-EXP, in process repl-thread(9). ; Warning: Returning from unknown block nilBlock ; While executing: PARENSCRIPT::RETURN-EXP, in process repl-thread(9). ; Warning: Returning from unknown block nilBlock ; While executing: PARENSCRIPT::RETURN-EXP, in process repl-thread(9). ; Warning: Trying to (RETURN TRUE) from inside a loop with an implicit nil block (DO, DOLIST, DOTIMES, etc.). Parenscript doesn't support returning values this way from inside a loop yet! ; While executing: #<Anonymous Function #x9D6C98E>, in process repl-thread(9). ; Warning: Returning from unknown block nilBlock ; While executing: PARENSCRIPT::RETURN-EXP, in process repl-thread(9). ; Warning: Returning from unknown block nilBlock ; While executing: PARENSCRIPT::RETURN-EXP, in process repl-thread(9). ; Warning: Returning from unknown block nilBlock ; While executing: PARENSCRIPT::RETURN-EXP, in process repl-thread(9). Result: (...) /** Check if ITEM is a member of ARR. */ function member(item, arr) { for (var el = null, _js_idx176 = 0; _js_idx176 < arr.length; _js_idx176 += 1) { el = arr[_js_idx176]; if (el === item) { break; }; }; return false; }; (...) Regards, -- Jacek Złydach, http://temporal.pr0.pl/devblog TRC - Bringing you tomorrow's solutions yesterday.

2 3

[parenscript-devel] Conditional nesting of lisp and javascript code
by Slobodan Milnović 02 Jun '11

02 Jun '11

Hi! I'm not sure what expressions/terms should I use for my situation, but I'll try my best to explain it. I have several functions combined under one ps:ps, and I'd like to create different code depending on my, let's call it debug variable. I have tried something like this: (ps:ps (defun my-function (some-var) (ps:lisp (when (= my-debug-level debug-level-of-this-code) (ps:ps (ps:chain console (log "works!!!"))))) (generate some fancy regular javascript code))) Unfortunatelly, when the inner ps does its thing, it creates an string, which then outer ps just attaches (and escapes appropriately) as string, not as additional javascript code that is to be attached to the rest. Is it possible to do this, or do I have to rethink my code?

3 5

[parenscript-devel] js-expander broken with recent changes to slime
by Andy Peterson 01 Jun '11

01 Jun '11

Recent changes to slime (quicklisp version) have broken the js-expander Slime Changelog: 2011-03-09 Helmut Eller <heller(a)common-lisp.net> Remove slime-sexp-at-point-for-macroexpansion. * slime.el (slime-sexp-at-point-for-macroexpansion): Deleted. (slime-eval-macroexpand): Use slime-sexp-at-point instead. (slime-eval-macroexpand-inplace): Use slime-bounds-of-sexp-at-point directly. I believe this fix should work but my slime fu is weak. $ diff js-expander.el ../../js-expander.el 40c40 < (first (slime-sexp-at-point-for-macroexpansion)) --- > (slime-sexp-at-point)

3 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

parenscript-devel May 2011