parenscript-devel July 2012

parenscript-devel@common-lisp.net

4 participants
8 discussions

Re: [parenscript-devel] four patches to PS-LOOP etc.
by Boris Smilga 11 Aug '12

11 Aug '12

On 21 Jul 2012, at 14:01, Vladimir Sedach wrote: > [...] Because patch 0003 causes all LOOPs to be > wrapped in blocks, and loop is used in various places, this means that > this code: > > (defun hello-world (&key ((:my-name-key my-name) 1)) > my-name) > > Used to look like: > > function helloWorld() { > var _js2 = arguments.length; > for (var n1 = 0; n1 < _js2; n1 += 2) { > switch (arguments[n1]) { > case 'my-name-key': > myName = arguments[n1 + 1]; > }; > }; > var myName = 'undefined' === typeof myName ? 1 : myName; > return myName; > }; > > And now looks like: > > function helloWorld() { > nilBlock: { > var _js2 = arguments.length; > for (var n1 = 0; n1 < _js2; n1 += 2) { > switch (arguments[n1]) { > case 'my-name-key': > myName = arguments[n1 + 1]; > }; > }; > }; > var myName = 'undefined' === typeof myName ? 1 : myName; > return myName; > }; > > I need a bit of time to think about the right way to fix that > (probably by fixing block not to emit if the body contains no return, > since it is all lexical) [...] Another approach would be to introduce a special PS-LOOP keyword (called NOBLOCK or something in the same vein) which would make LOOP expand to PROGN rather than to BLOCK. Then we could add the keyword to the internal LOOPs and get the PROGNs back. This is simpler than checking for RETURNs, though not necessary more elegant. That said, I don't quite see from the example above why the issue needs fixing in the first place. You can't really mean that the block introduces local scope for myName etc.? — JavaScript doesn't have block scope. So what is your idea? Yours, — B. Smilga.

2 2

[parenscript-devel] Problem using parenscript with ECL
by Magnus Malm 08 Aug '12

08 Aug '12

Hi, I am having problems loading parenscript with ECL. I use quicklisp to load parenscript. My system: Linux 2.6.32-38-generic #83-Ubuntu SMP Wed Jan 4 11:12:07 UTC 2012 x86_64 GNU/Linux Versions: - ECL 12.7.1 (git:e1fdb85bdaca39ad2d2ed06647c7f34cd0ff3585) - Quicklisp 2012-07-03 - named-readtables 2010-10-06 (named-readtables-20101006-darcs.tgz, according to quicklisp) - parenscript 2.4 When I try to load parenscript, I get the following: ---- > (ql:quickload "parenscript") To load "parenscript": Load 1 ASDF system: named-readtables Install 3 Quicklisp releases: anaphora cl-ppcre parenscript ; Fetching #<url "http://beta.quicklisp.org/archive/cl-ppcre/2010-10-06/cl-ppcre-2.0.3.tgz"> ; 153.97KB ================================================== 157,665 bytes in 0.04 seconds (4276.94KB/sec) ; Fetching #<url "http://beta.quicklisp.org/archive/anaphora/2011-06-19/anaphora-0.9.4.tgz"> ; 5.02KB ================================================== 5,136 bytes in 0.00 seconds (0.00KB/sec) ; Fetching #<url "http://beta.quicklisp.org/archive/parenscript/2012-02-08/parenscript-2.4.tgz"> ; 131.45KB ================================================== 134,604 bytes in 0.03 seconds (4107.79KB/sec) ; Loading "parenscript" [package anaphora]................................ [package anaphora-basic].......................... [package anaphora-symbol]......................... [package cl-ppcre]............................. ;;; Error: ;;; in file package.lisp, position 263 ;;; at (in-readtable parenscript) ;;; * The macro form (editor-hints.named-readtables:ensure-readtable ':parenscript) was not expanded successfully. ;;; Error detected: ;;; (editor-hints.named-readtables:ensure-readtable ':parenscript) is not of type editor-hints.named-readtables:named-readtable-designator. Condition of type: COMPILE-ERROR Error while invoking #<compile-op (:VERBOSE NIL) 0000000004ab02a0> on #<cl-source-file "parenscript" "src" "package"> Available restarts: 1. (TRY-RECOMPILING) Try recompiling package 2. (RETRY) Retry compiling #<cl-source-file "parenscript" "src" "package">. 3. (ACCEPT) Continue, treating compiling #<cl-source-file "parenscript" "src" "package"> as having been successful. 4. (ABORT) Give up on "parenscript" 5. (RESTART-TOPLEVEL) Go back to Top-Level REPL. Broken at SI:BYTECODES. [Evaluation of: (QUICKLISP-CLIENT:QUICKLOAD "parenscript")] In: #<process TOP-LEVEL>. ---- Anyone who have had the same problem? It loads fine with SBCL on the same machine, and the same quicklisp setup. Any help or pointers would be much appreciated. -- Magnus Malm

2 3

[parenscript-devel] :join isn't being interpreted as a javascript function
by Russell Sim 31 Jul '12

31 Jul '12

Hi, I think I have encountered a bug while using the who-ps-html macro. (who-ps-html (:li (:img :src icon :size 40) (:p message) (:span :class "author" name) (:span :class "date" timestamp))) The first expansion of the who-ps-html yields, (STRINGIFY "<LI><IMG SRC=\"" ICON "\" SIZE=\"40\">" MESSAGE "" NAME "" TIMESTAMP "</LI>") But the javascript generated is, ['<LI><IMG SRC="', icon, '" SIZE="40">', message, '', name, '', timestamp, '</LI>']['join']('') I have been able to get the correct behaviour by applying the following patch, since join is a symbol that is imported via the ps-js-symbols package. commit 86d39309692987644798148e24fd67b70667eaa7 (HEAD, refs/heads/master) Author: Russell Sim <russell.sim(a)gmail.com> Date: Tue May 29 09:12:30 2012 +1000 Fixed :join bug in stringify expansion. Modified src/non-cl.lisp diff --git a/src/non-cl.lisp b/src/non-cl.lisp index 387bd29..f2ed0e7 100644 --- a/src/non-cl.lisp +++ b/src/non-cl.lisp @@ -203,7 +203,7 @@ (defpsmacro stringify (&rest things) (if (and (= (length things) 1) (stringp (car things))) (car things) - `((@ (list ,@things) :join) ""))) + `((@ (list ,@things) join) ""))) (defun stringify (&rest things) "Like concatenate but prints all of its arguments." (format nil "~{~A~}" things)) Cheers, Russell

3 4

[parenscript-devel] Parenscript onsubmit="return validate()"
by Juan Reynoso Elias 29 Jul '12

29 Jul '12

*Hello I work with parenscript and UCW, I need validate some input text and I have control the submit of the form.* *Here use parenscript, it's a code for my function "validate" ** ( setf xvalue document.form1.mac.value ) (setf result ((@(regex "/([A-Fa-f0-9]{2,2}:{1}){5}([A-Fa-f0-9]{2})$/") test) xvalue )) (if (eql F **result** ) ((alert "Fail") (setf document.form1.mac.style.background-color "red") F ) ; ==> javascript return false; (alert "Ok") T)) ; ==> javascript return true;* *Html code , called function validate **<form id="form1" onsubmit="return validate();" > Here, I have a question, How I do same with parenscript *>> *"return validate();"* (<ucw:form :name "form1" :onsubmit (ps (validate) ; *Here I have a problem* * *>> *"return validate();"* *(*defun validate () * ( setf xvalue document.form1.mac.value ) (setf result ((@(regex "/([A-Fa-f0-9]{2,2}:{1}){5}([A-Fa-f0-9]{2})$/") test) xvalue )) (if (eql F **result** ) ((alert "Fail") (setf document.form1.mac.style.background-color "red") F ) ; ==> javascript return false; (alert "Ok") T))) ; ==> javascript return true;* -- I.S.C. Juan Reynoso Elias Departamento de Soporte Técnico del Instituto de la Función Registral del Estado de México. Vicente Guerrero 102, Col Santa Ana Tlapaltitlán, Toluca, Méx. C.P. 50160. Tel. 2106852.

2 1

[parenscript-devel] create object doesn't accept symbols
by Russell Sim 29 Jul '12

29 Jul '12

Hey, I have hit another small bug while I was using some older code which was using quoted symbols as keys when defining an object. For example when I evaluate CL-USER> (ps:ps (ps:create 'test "bang" 'symbol-saved-my-life "parenscript")) I get the following error. Slot key 'TEST is not one of symbol, string or number. [Condition of type SIMPLE-ERROR] I have personally been using keywords instead of quoted symbols but it seems there was a time when quoted symbols were ok and the documentation seems to suggest that symbols should be fine? The following patch enables quoted symbols to work again and will convert them to the appropriate camelCase form. CL-USER> (ps:ps (ps:create 'test "bang" 'symbol-saved-my-life "parenscript")) "({ 'test' : 'bang', 'symbolSavedMyLife' : 'parenscript' });" Cheers, Russell commit 84d94815b1655179b283627a64bf6ed1ac1dba07 (HEAD, refs/heads/master) Author: Russell Sim <russell.sim(a)gmail.com> Date: Sat Jun 2 14:48:20 2012 +1000 Allow quoted strings to be used as keys in objects Modified src/non-cl.lisp diff --git a/src/non-cl.lisp b/src/non-cl.lisp index f2ed0e7..5cba0a8 100644 --- a/src/non-cl.lisp +++ b/src/non-cl.lisp @@ -52,12 +52,18 @@ `(ps-js:object ,@(loop for (key val-expr) on arrows by #'cddr collecting (progn - (assert (or (stringp key) (numberp key) (symbolp key)) - () - "Slot key ~s is not one of symbol, string or number." - key) - (cons (aif (and (symbolp key) (reserved-symbol? key)) it key) - (compile-expression val-expr)))))) + (assert (or (stringp key) (numberp key) (symbolp key) (eq 'quote (car key))) + () + "Slot key ~s is not one of symbol, string or number." + key) + (cons (acond + ((and (symbolp key) (reserved-symbol? key)) + it) + ((and (consp key) (eq 'quote (car key))) + (symbol-to-js-string (eval key))) + (t + key)) + (compile-expression val-expr)))))) (define-expression-operator %js-getprop (obj slot) (let ((expanded-slot (ps-macroexpand slot))

2 1

[parenscript-devel] Inconsistent compilation of the empty list?
by Daniel Gackle 27 Jul '12

27 Jul '12

I have some test data where occasionally an empty list appears as an element inside of some other list. It's getting compiled to the JS string "[]" when what I need is the array literal [], in a way that seems inconsistent. Specifically, these are good: PS> (ps []) "[];" PS> (ps '()) "[];" PS> (ps '(1 2)) "[1, 2];" But these are not, because they generate either the string '[]' or null as the second element, when what I need is the array literal []: PS> (ps '(1 [])) "[1, '[]'];" PS> (ps '(1 ())) "[1, null];" Is this an inconsistency? Is there a workaround? Daniel

2 1

[parenscript-devel] top-level LET and LET* will not create global variables
by Yakov Zaytsev 27 Jul '12

27 Jul '12

Is this expected? CL-USER> (ql:quickload "parenscript") ... CL-USER> (defpackage :ps-user (:use :cl :ps)) #<The PS-USER package, 0/16 internal, 0/16 external> CL-USER> (in-package "PS-USER") #<The PS-USER package, 0/16 internal, 0/16 external> PS-USER> (ps (let ((s-a)))) "(function () { var sA = null; return null; })();" Also, $ cat foo.lisp (let ((s-a)) (+ s-a 42) (chain s-a (append-child foo))) PS-USER> (ps-compile-file "foo.lisp") "(function () { var sA = null; sA + 42; return sA.appendChild(foo); })(); " PS-USER> Which is against documentation "Top-level LET and LET* forms will create new global variables, or overwrite the values of already existing global variables with the same name." Please comment

3 2

[parenscript-devel] four patches to PS-LOOP etc.
by Boris Smilga 21 Jul '12

21 Jul '12

Dear parenscript-devel, please find attached three patches to the implementation of looping constructs in Parenscript. The first provides a more complete support for CL-LOOP conditional clauses, so that it becomes possible to write, e. g.: (loop for i :from 0 :to 5 for x := (foo i) when x collect x and if (oddp x) collect (1+ x) else collect (/ x 2) end and do (alert x)) The second patch implements WITH clauses with implicit initialization (though not with TYPE-SPECs), e. g. (loop for i :from 0 :to 5 with x unless (foo i) do (return (setf x i))) Formerly, this produced incorrect code, because PS-LOOP required explicit initialization of such variables, but failed to properly assert that the entity following the variable name is the keyword := . The third patch implements NAMED and RETURN clauses. Also, it fixes the problem that PS-LOOP (contrary to CL-LOOP) did not establish an implicit BLOCK, which used to cause "Returning from unknown block nilBlock" warnings when RETURN forms were used inside LOOPs. The fourth patch fixes fallacious generated returns in JavaScript code where RETURN or RETURN-FROM are used inside conditional expressions inside loops, as in: (block nil (dotimes (i 10) (if (test i) (return i))) (return -1)) This produced the following JavaScript: (function () { var loopResultVar1 = null; for (var i = 0; i < 10; i += 1) { if (test(i)) { loopResultVar1 = i; break; }; }; return loopResultVar1; return -1; })(); If test() fails for all values of i, this code evaluates to null. The meaning of the original code, however, is for the expression to evaluate to -1. So it goes. Yours, — B. Smilga.

2 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

parenscript-devel July 2012