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

ES6 imports
by Drew Jose 03 Apr '24

03 Apr '24

This is currently in the todo stage, but until then is there a way to give some statement explicitly? like (inline-js "import {x} from y;")

2 1

JS string interpolation
by Drew Jose 03 Apr '24

03 Apr '24

I was wondering if there was any syntax for using JavaScript template literals like (literal "hello ${variable-name}") Output: `hello ${variableName}`

3 2

Classes, updating parenscript
by Monstara 22 Feb '23

22 Feb '23

Hi, there could be a discussion whether to "modernize" parenscript, since ECMAScript moves faster than is customary in Lisp. I have started studying and playing with the parenscript code, and I am interested in adding some newer ECMA features. First off, let me say that I was unable to call (super) inside a constructor, the way paren6 works (since the prototype is explicitly set after the class function is declared). Therefore I feel it would be better if the compiler itself supports js classes. Once I get better acquainted with the compiler, would there be an interest in other ECMA features being added? I don't know, maybe async? Or something else. I'm open to suggestions. I have started a prototype of classes already, but I've yet to learn. Any pointers would be appreciated. Regards, Mois

2 2

Adding CL:TAGBODY for SERIES support
by Andrew Easton 10 Feb '23

10 Feb '23

Hello everyone, It seems valuable to compile SERIES [1] macros with PARENSCRIPT [2], however, parenscript does not currently seem to support CL:TAGBODY [3,4]. Even poking around the HyperSpec and discovering that CL:DO provides *not* an implicit progn, but an implicit tagbody [5], does not help. The (PARENSCRIPT:DO ...)-form only has an implicit progn around the body [3]. I have started to implement TAGBODY for PARENSCRIPT [A,B,C]. The general idea is to imitate a jump table by looping over a switch-case. A GO (C-terminology: jump) then sets the switch-variable to the next jump destination. The loop subsequently causes the switch to branch to the jump target in the switch-variable. Leaving the tagbody means leaving the loop. There are complications. Common Lisp allows nested tagbody-forms. Common Lisp allows go-tags to be referenced within the lexical scope *and* the dynamic extent of a tagbody form. This means that a LAMBDA can close over a go-tag and jump there, see an example in [B], of how inconvenient this can become for compilation to JavaScript. PARENSCRIPT is well-designed. Its compilation of BLOCKs, LOOPs and SWITCHes seems to permit compilation of a TAGBODY to JavaScript code. PARENSCRIPT even handles RETURNing from a BLOCK via a LAMBDA by automatically creating a JavaScript try-catch. This seems to curb the inconveniences brought on by lexical closures jumping to go-tags in the TAGBODY's dynamic extent. I need help in the following points: 1. I need a code review of the algorithm. The implementation in [B] seems to be satisfactory. There are some test cases and examples. Most there is the most hairy example I could find up to now. I may have missed crucial details. 2. My understanding of the CL:TAGBODY definition in the CLHS [4] may be wrong. Which alternate interpretations does anybody here know of? 3. What examples of PARENSCRIPT:DEFPSMACRO do you know, that might help me understand its semantics? I would hazard a guess at DEFPSMACRO being a facility to add TAGBODY to PARENSCRIPT, however, my understanding of DEFPSMACRO is very bad and I do not know where to start tinkering with it to further my understanding. Kind regards, Andrew Easton === Attachments === [A] 2022-05-20_defmacro-series-expand.lisp [B] 2022-05-20_parenscript-devel_tagbody-code-short.lisp [C] 2022-05-20_parenscript-devel_tagbody-code-long.lisp The long version contains some dead-ends that were encountered during development. This is an important source of counter-examples. === References === [1] The SERIES macro package a. https://www.cs.cmu.edu/Groups/AI/html/cltl/clm/node347.html#SECTION00340000… b. https://www.cs.cmu.edu/Groups/AI/html/cltl/clm/node362.html#SECTION00350000… c. https://dspace.mit.edu/handle/1721.1/6035 d. https://dspace.mit.edu/handle/1721.1/6031 e. (ql:quickload :series) f. https://sourceforge.net/projects/series/ [2] Parenscript https://parenscript.common-lisp.dev/ [3] Parenscript Reference manual (updated 2019-10-15) https://parenscript.common-lisp.dev/reference.html [4] Common Lisp HyperSpec (CLHS) entry for CL:TAGBODY http://www.lispworks.com/documentation/HyperSpec/Body/s_tagbod.htm#tagbody [5] Common Lisp HyperSpec (CLHS) entry for CL:DO http://www.lispworks.com/documentation/HyperSpec/Body/m_do_do.htm#do

4 11

function "at" is undefined
by David O'Toole 14 Dec '22

14 Dec '22

Using the dot syntax for identifiers works (with a warning), but (@ a b) and (getprop a b) don't work, the functions are undefined. What am I doing wrong?

2 2

Re: Regression problem in loop macro between Parenscript 2.6 and 2.7.1
by Piotr Wasik 02 Aug '20

02 Aug '20

Hi again, I actually "fixed" the break-in-function-body problem by replacing compile-loop-body function with the old version. Cheers, Piotr

1 0

Regression problem in loop macro between Parenscript 2.6 and 2.7.1
by Piotr Wasik 02 Aug '20

02 Aug '20

Hi, Problem number 1: This form (ps (loop :for i :from 0 :do (print i))) generates: (function () { for (var i = 0; i <= null; i += 1) { print(i); }; })(); I fixed it locally by changing for-from (defun for-from (from-key var state) (unless (atom var) (err "an atom after FROM" var)) (let ((start (eat state)) (op (loop-case from-key (:downfrom '-) (otherwise '+))) (test-op nil) (by nil) (end nil)) (loop while (member (as-keyword (peek state)) '(:to :below :downto :above :by)) do (let ((term (eat state))) (if (eq (as-keyword term) :by) (setf by (eat state)) (setf op (loop-case term ((:downto :above) '-) (otherwise op)) test-op (loop-case term (:to (loop-case from-key (:downfrom '>=) (otherwise '<=))) (:below '<) (:downto '>=) (:above '>)) end (eat state))))) (let ((test (when test-op (list test-op var (maybe-hoist end state))))) (push-iter-clause `(,var ,start (,op ,var ,(or by 1)) ,test) state)))) The difference is that test-op is assigned initially nil, and only re-assigned a value if there is a term. In my example I get infinite loop, but the same behaviour happens if I have more looping constructs, e.g. (loop :for i :from 0 :for j :in list :do (print i)) Problem number 2: Let causes the whole body of loop to be wrapped in function, whereas the previous version wrapped it in with ({ i : i }) { .... } Example: (ps (loop :for i :from 0 :for j :in (array 1 2 3) :do (let ((i i)) (lambda () i)))) generates (function () { var _js207 = [1, 2, 3]; var _js209 = _js207.length; var FIRST210 = true; for (var i = 0; true; i += 1) { (function () { var _js208 = FIRST210 ? 0 : _js208 + 1; if (_js208 >= _js209) { break; }; var j = _js207[_js208]; var i211 = i; function () { return i211; }; return FIRST210 = null; })(); }; })(); The diference is that it is illegal to break from a function body, and it was legal to break from with. Can somebody help please? Cheers, Piotr

1 0

Announce: Paren6 - an ES6-like library for Parenscript
by Ben McGunigle 08 Oct '19

08 Oct '19

Hi Parenscripters, I have started a collection of ES6 macros for Parenscript. It's available at https://github.com/BnMcGn/paren6 A quick review or two would be nice before I post to quicklisp. This is different from Peter Stirling's work at https://github.com/vsedach/Parenscript/pull/39 primarily because the paren6 library does not attempt to produce ES6 output. Paren6 is usable with current versions of Parenscript and outputs ES5 code. The goal is to provide Parenscript users with analogues of ES6 features. When Parenscript supports ES6 natively, these macros might be useful for earlier *js-target-version* support. Feel free to incorporate anything useful - code or interface - into Parenscript. Ben

3 2

[patch] ps-macro-function
by Ben McGunigle 25 Sep '19

25 Sep '19

Hi parenscript people, I need to alias a parenscript macro [macrolet saga omitted], and I don't want to do it by directly tampering with the internal *macro-toplevel* hash table. This defsetf ps-macro-function seems like the right thing to do. Please let me know if I have missed an obvious existing solution. Thanks, Ben

1 0

Overriding cl package symbols
by James Gunn 10 Jun '19

10 Jun '19

Hello, I have been reading the source code for parenscript and I am keen to find out how you override locked symbols? In the parenscript package there are exports such as "#:defun". I have tried myself to create my own package that exports defun but i get the following error message(using SBCL) "Lock on package COMMON-LISP violated when proclaiming DEFUN as a function" I'd be very interested in finding out how you got around this. Thank you, James Gunn

2 1