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

[parenscript-devel] The next frontier?
by Daniel Gackle 01 Mar '10

01 Mar '10

Congratulations on the new release! This seems like a good time to ask: what (if any) are the next significant things that could and should be added to Parenscript? Put differently, what CL constructs are there that (a) haven't been tackled yet, and (b) have a reasonable mapping to JS? The latter is important to preserve the goals of efficient, readable, debuggable JS. Any suggestions? I nominate backquote/comma. At least at a 50,000 foot level, it seems like the sort of thing PS could do, and it's pretty obvious that it would be useful. Daniel

4 7

[parenscript-devel] New Parenscript version
by Vladimir Sedach 27 Feb '10

27 Feb '10

Exciting things in this release include the long-awaited implicit return functionality, multiple value return, a completely redone and updated manual in HTML format, and many bugfixes. The version naming scheme has now been changed to a <major>.<minor> format (the new release is version 2.1). Enjoy! Vladimir

1 0

[parenscript-devel] Skipping null returns at the top level.
by szergling 27 Feb '10

27 Feb '10

Hi folks, I was wondering if there's an idiom for skipping the generation of a form completely at the top-level. This is mildly related to the implicit return feature currently being trialled. Here's an example: suppose I'm trying to skip over this form: (in-package :something-something) by using (defpsmacro in-package (x) nil) An in-package form then compiles to "null;" This spurious output may result in errors (I'm using ps to convert my Lisp code to Actionscript). How about using (values) to indicate explicitly that something doesn't have any return values? Yong.

2 8

[parenscript-devel] Discrepancy in MULTIPLE-VALUE-BIND
by Daniel Gackle 23 Feb '10

23 Feb '10

Looks like our implementation doesn't match CL's after all. (blah2-call) evaluates to (2 5) in Common Lisp, but [2, undefined] in Parenscript. (defun blah1 () (values 2 5)) (defun blah2 () (blah1)) (defun blah2-call () (multiple-value-bind (a b) (blah2) (list a b))) Daniel

2 2

[parenscript-devel] Symbol-macro clashes
by szergling 13 Feb '10

13 Feb '10

Hi list, Just a quick note. Something I discovered a while ago, which hasn't quite been affected by recent patches. There's a potential clash between symbol macros and normal symbols in parenscript. Sometimes, we don't want to macroexpand certain symbols: In Common Lisp, PS> (define-symbol-macro %cldata (list 1 2 3)) %CLDATA PS> (let ((%cldata (list 4 5 6))) %cldata) (4 5 6) In parenscript, PS> (define-ps-symbol-macro %data (list 1 2 3)) %DATA PS> (ps %data) "[1, 2, 3];" PS> (ps (let ((%data (list 2 4 5))) %data)) ; Evaluation aborted. The value (ARRAY 1 2 3) is not of type SYMBOL. [Condition of type TYPE-ERROR] The %data (binding) shouldn't be expanded, and the %data in the let body should now be "shadowed" by the new binding. This also occurs with LET*, FLET, and LABELS (what else have I missed?). I couldn't looked too closely, but recently, all the variable binding seem to have been refactored into the code for ps-special-form var, so perhaps this is now easier to fix. Cheers, Yong.

2 1

[parenscript-devel] Sharing code between client and server?
by Axel Rauschmayer 03 Feb '10

03 Feb '10

I would like to use Parenscript with ABCL and am hoping for a GWT-like experience. What is the best way to share code between client and server? - Do I use the Parenscript constructs on the server? Not having CLOS seems a shame. - How would one send objects between client and server? - As JSON? How would the conversion be performed? Thanks! Axel -- Axel Rauschmayer axel(a)rauschma.de http://www.pst.ifi.lmu.de/people/staff/rauschmayer/axel-rauschmayer/ http://2ality.blogspot.com/ http://hypergraphs.de/

2 2