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

Re: Proper way to console.log in Parenscript?
by Vladimir Sedach 22 May '19

22 May '19

Hi Doug, There are a couple of ways: https://common-lisp.net/project/parenscript/reference.html#section-objects Something like (funcall (ps:getprop console 'log) "text") works. Vladimir

1 0

Proper way to console.log in Parenscript?
by Doug Beney 13 May '19

13 May '19

Hi, I was using (console.log "my message"). I see there's a message about dot operators becoming deprecated. I'm curious what's the most intuitive way to access the console.log function, or a similar one, with Parenscript. Thanks!

1 0

An issue where defsetf doesn't work for a symbol defined by symbol-macrolet
by Seki_GMail 11 Apr '19

11 Apr '19

Hi, Thanks for your great project. I found an issue where defsetf doesn't work for a symbol defined by symbol-macrolet. The detail is the following. ## environment - version of Parenscript - latest of master (526346549f0342d67947d360a8f7ba9fc7b09e54) - CL Implementation (same result in both) - SBCL 1.5.0 - Clozure CL 1.11.5 ## code to reproduce ```lisp (use-package :parenscript) (princ (ps (defun my-car (lst) (nth 0 lst)) (defun my-set-car (lst value) (setf (nth 0 lst) value)) (defsetf my-car (lst) (value) `(my-set-car ,lst ,value)) ;; Raw setf is ok (setf (my-car lst) 100) ;; setf for macrolet symbol is NG (symbol-macrolet ((sym (my-car lst))) (setf sym 300)))) ``` Then, the result is the following. (I added some comments for convenience.) ```javascript function myCar(lst) { __PS_MV_REG = []; return nth(0, lst); }; function mySetCar(lst, value) { __PS_MV_REG = []; return nth(0, lst) = value; }; /* Raw setf is ok */ (function () { var _js66 = lst; var _js65 = 100; __PS_MV_REG = []; return mySetCar(_js66, _js65); })(); /* setf for macrolet symbol is NG */ myCar(lst) = 300; ``` Thanks. Regards, -- Eiji, Seki (hamgoostar(a)gmail.com) https://github.com/eshamster

2 2

Implement importing and exporting ES Modules
by Moritz.Hedtke 03 Apr '19

03 Apr '19

Hello, recently I tried to use ES Modules with Parenscript so I modified the code. I just wanted to share the patch - maybe you want to include it in the official repository. Kind regards, Moritz Hedtke From 4862600435c3dfbf4b329b5d4578e5ae77f9eaa2 Mon Sep 17 00:00:00 2001 From: mohe2015 <mohe2015(a)users.noreply.github.com> Date: Sun, 24 Mar 2019 13:00:31 +0100 Subject: [PATCH] Implement importing and exporting ES Modules --- src/js-ir-package.lisp | 4 ++++ src/package.lisp | 6 ++++++ src/printer.lisp | 15 +++++++++++++++ src/special-operators.lisp | 12 ++++++++++++ 4 files changed, 37 insertions(+) diff --git a/src/js-ir-package.lisp b/src/js-ir-package.lisp index dd5fa80..46aefc7 100644 --- a/src/js-ir-package.lisp +++ b/src/js-ir-package.lisp @@ -144,4 +144,8 @@ #:funcall #:escape #:regex + #:export + #:export-default + #:import + #:import-default )) diff --git a/src/package.lisp b/src/package.lisp index 2a39628..3262cc8 100644 --- a/src/package.lisp +++ b/src/package.lisp @@ -150,6 +150,12 @@ ;; compile-time stuff #:eval-when + ;; modules + #:export + #:export-default + #:import + #:import-default + ;; body forms #:progn diff --git a/src/printer.lisp b/src/printer.lisp index fc52e71..df94dfa 100644 --- a/src/printer.lisp +++ b/src/printer.lisp @@ -415,3 +415,18 @@ vice-versa.") ;; literal-js should be a form that evaluates to a string containing ;; valid JavaScript (psw literal-js)) + +(defprinter ps-js:export (object) + "export " (ps-print object)) + +(defprinter ps-js:export-default (object) + "export default " (ps-print object)) + +(defprinter ps-js:import (file objects) + "import { " + (loop for (object . remaining) on objects do + (psw object) (when remaining (psw ", "))) + " } from " (ps-print file)) + +(defprinter ps-js:import-default (file name) + "import " (psw name) " from " (ps-print file)) diff --git a/src/special-operators.lisp b/src/special-operators.lisp index a3abc90..4a90683 100644 --- a/src/special-operators.lisp +++ b/src/special-operators.lisp @@ -702,3 +702,15 @@ code in :execute." (if (member :execute situation-list) (ps-compile `(progn ,@body)) (ps-compile `(progn)))) + +(define-expression-operator export (object) + `(ps-js:export ,(ps-compile object))) + +(define-expression-operator export-default (object) + `(ps-js:export-default ,(ps-compile object))) + +(define-expression-operator import (file &rest objects) + `(ps-js:import ,file ,objects)) + +(define-expression-operator import-default (file name) + `(ps-js:import-default ,file ,name))

1 0

Parenscript no longer compiles on LispWorks
by Jens Nevens 04 Mar '19

04 Mar '19

Hello I opened an issue on the Parenscript GitHub page, since Parenscript no longer seems to compile on LispWorks. Instead of repeating the bug here, I will simply paste the link: https://github.com/vsedach/Parenscript/issues/45 <https://github.com/vsedach/Parenscript/issues/45> Kind regards, Jens Nevens <jens.nevens(a)gmail.com>

1 0

Parenscript 2.7 released
by Vladimir Sedach 02 Dec '18

02 Dec '18

Hello, Parenscript 2.7 has been released. You can find the tarball at: https://common-lisp.net/project/parenscript/release/parenscript-2.7.tgz https://common-lisp.net/project/parenscript/release/parenscript-2.7.tgz.sig 2.7 should be available in Quicklisp in the near future. A detailed list of the changes in this release can be found in the repository commit history: https://gitlab.common-lisp.net/parenscript/parenscript/commits/master Vladimir

1 0

Re: ES2015 features?
by John Pallister 16 Nov '18

16 Nov '18

Thanks to Peter and Samantha for their feedback, and particularly to Vladimir for the roadmap. Your thoughts on the licensing were very interesting also. It's great to know that Parenscript is alive and kicking! Cheers, John :^P -- John Pallister john(a)johnp.net john(a)synchromesh.com

1 0

Re: ES2015 features?
by William Halliburton 16 Nov '18

16 Nov '18

Yes. Please more detail on the licensing. On Tue, Nov 13, 2018 at 12:42 PM Vladimir Sedach <vas(a)oneofus.la> wrote: > Hi John, > > > I realise that pretty much all of these are just syntactic sugar, but I > > wanted to ask whether anyone other than me thinks it would be nice if > > Parenscript knew about these modern niceties and could be directed to > > generate them, and what the general roadmap (if any) is for Parenscript, > > before I start looking at what's involved. > > Adding support for newer ECMAScript features in Parenscript output is > part of the plan. There is a variable *JS-TARGET-VERSION* that > controls the ECMAScript version the output will target. Peter > Stirling has already started work towards ECMAScript 2015: > https://github.com/vsedach/Parenscript/pull/39 > > The general road-map I have in mind is, first, to release Parenscript > 2.7. I plan to make 2.7 the last 2.x Parenscript release. > > After the release, the Parenscript code will become part of > Parenscript 3, which will have some incompatible changes: removal of > deprecated macros and special operators, and different system and > package names (to prevent conflicts between Parenscript 2.x and 3, > and to no longer define short two and four letter package names, > which conflict with people's package nicknames in their systems and > the REPL). > > I also have a pile of ideas for improving the internals of the > Parenscript compiler, and improvements in the efficiency and > correctness (with respect to Common Lisp semantics) of the generated > Parenscript code, that are non-breaking changes. > > The most significant change for Parenscript 3 will be the license: > Parenscript 3 will incorporate the 3 clause BSD licensed Parenscript > 2 code into a copyleft (GPL version 3 or later) project. There are a > lot of reasons for this that I can go into in more detail, if anyone > is interested. The short explanation is that my experiences in the > past six years have very strongly convinced me that working on > non-copyleft Free Software is against my own (and the general > public's) interests. I have decided to re-license Free Software > projects that I created or maintain under the GPL. > > Vladimir > >

2 1

ES2015 features?
by John Pallister 13 Nov '18

13 Nov '18

Hello list, After admiring Parenscript from afar for many years I'm finally taking the plunge into web front-end development. I'm using Preact <https://preactjs.com/> with Parenscript - so far so good. After reading the article How to make your React app fully functional, fully reactive, and able to handle all those crazy side effects <https://medium.freecodecamp.org/how-to-make-your-react-app-fully-functional…> I would like to incorporate Redux, Cycle.js and Immutable.js, by porting redux-cycles <https://github.com/cyclejs-community/redux-cycles> to Preact (and Parenscript). Looking at the sample code, these modern JavaScript libraries (particularly the more functional ones) make heavy use of ES2015 features such as: - Arrow functions - const - let - Spread properties <https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators…> - Rest parameters <https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Functions…> - Destructured function parameters - etc. I realise that pretty much all of these are just syntactic sugar, but I wanted to ask whether anyone other than me thinks it would be nice if Parenscript knew about these modern niceties and could be directed to generate them, and what the general roadmap (if any) is for Parenscript, before I start looking at what's involved. Thanks very much, John :^P -- John Pallister john(a)johnp.net john(a)synchromesh.com

4 4

An apology for intruding into parenscript management
by Philipp Marek 09 Nov '18

09 Nov '18

Hi, a few hours ago I got an email with subject Request to join the parenscript group and, believing that I'm involved in the gitlab parenscript project, I went right ahead and ack'ed that. But just a minute later I got to know why I really got the email - not because of parenscript project membership, but because Erik H made me gitlab maintainer just an hour ago! So I want to apologize - I granted access to Jans Aasman from the wrong "role", and now feel like an intruder. Please tell me what to do - should I revoke that access again and apologize to Jans (too), or is it okay (this one time)? I promise to be more careful in the future ;/ Regards, Phil

1 0