parenscript-devel November 2018

parenscript-devel@common-lisp.net

6 participants
5 discussions

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

Upcoming 2.7 release
by Vladimir Sedach 09 Nov '18

09 Nov '18

Hello, I am planning to put together a 2.7 release soon. There have been many bugfixes and improvements in the generated code since 2.6. Please check out the latest code in the repository (https://gitlab.common-lisp.net/parenscript/parenscript.git) and let me know if you find any issues. Thank you, Vladimir

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

parenscript-devel November 2018