parenscript-devel

parenscript-devel@common-lisp.net

373 discussions

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

ACL readtable case and ps::encode-js-identifier
by Sky Hester 13 Oct '18

13 Oct '18

Hi, I opened an issue [1] for this on CL gitlab, then saw the mailing list info. At any rate, I was a little confused by how the :parenscript readtable behaves with ACL mlisp (case-sensitive-lower). It wasn't obvious to me at first, but I found a place in the utility function encode-js-identifier that swaps case for all-lowercase and all-uppercase symbols. Changing the readtable definition and disabling that case-swapping code (for allegro only) kept the intended behavior. Alternatively, you can use (excl:in-case-mode :common), but that's not very fun. See the gitlab issue for details, linked below. Fiddly, but maybe this will save someone a few minutes one day. -Sky [1] https://gitlab.common-lisp.net/parenscript/parenscript/issues/1

2 1

Git repository move to github and new mailing list
by Vladimir Sedach 28 Oct '13

28 Oct '13

Hi everybody, Based on several requests, I've moved the Parenscript git repository to Github: https://github.com/vsedach/Parenscript I encourage everyone to use the bug tracker there, as right now the bug tracker is my inbox (I have emails from over a year ago I haven't gotten around to addressing yet). I've also received several reports of mailing list weirdness ever since the botched move from Mailman for common-lisp.net mailing lists (which among other things has made the list archives inaccessible). I've decided to move the Parenscript mailing list to be hosted on Google Groups: http://groups.google.com/d/forum/parenscript Please address any future mailing list traffic there. Happy hacking, Vladimir

2 1

Fwd: trident-mode.el -- Interactive Parenscript development
by Olaf Ruppert 27 Sep '13

27 Sep '13

On Tue, Jul 23, 2013 at 7:41 PM, John Mastro <john.b.mastro(a)gmail.com> wrote: > Hello, > > I recently started working on an Emacs minor mode with the goal of using > SLIME[1] and Skewer[2] to make Parenscript development as dynamic as > possible. I'm calling it Trident, and it's online now at > https://github.com/johnmastro/trident-mode.el. > > Skewer, in case you're not familiar with it, allows you to send JavaScript > (amongst other things) directly from Emacs to the web browser. Trident's > general purpose is to use that ability to treat the browser's JavaScript > engine as just another Lisp image that we can send code to for evaluation. > Trident also provides commands for displaying the code generated by > Parenscript, which can be used without Skewer. > > If this interests you at all, try it out and let me know what you think. The > readme.org at the GitHub repo has more information on setup and usage. I > haven't gotten it on ELPA yet but it's a single file and a mere load or > require away. Hi, thank you very much for Trident! Awesome! Webdevelopment is fun again :) I'm currently use it every day. Is there a way to send the C-c C-k output also to a file? Best regards, Olaf > > Thanks, > > John Mastro > > [1] http://common-lisp.net/project/slime/ > [2] https://github.com/skeeto/skewer-mode

1 0

question on parencsript minification
by Eric Schulte 20 Aug '13

20 Aug '13

First off, my thanks to the parenscript developers. This is a very useful tool. To learn parenscript, I've thrown together the following little HTML5 web-page genetic programming image matching application. http://eschulte.github.io/gpolygon/ Everything works well, until I try to minimize or obfuscate the generated JavaScript. I think I must be misunderstanding how minimization works. I'm able to minimize this package using the following adopted from the reference manual. (defpackage :gpolygon (:use :common-lisp :hunchentoot :cl-who :parenscript :cl-fad) (:export :serve)) (in-package :gpolygon) (eval-when (:compile-toplevel :load-toplevel :execute) (setf *js-string-delimiter* #\") (setf *ps-print-pretty* nil) (obfuscate-package :gpolygon (let ((code-pt-counter #x8CF6) (symbol-map (make-hash-table))) (lambda (symbol) (or (gethash symbol symbol-map) (setf (gethash symbol symbol-map) (make-symbol (string (code-char (incf code-pt-counter)))))))))) However, many proper function names are changed which should not be (e.g., length, etc...). I've tried to include the ps-dhtml-symbols package to prevent this, but of course this package causes *many* conflicts with common lisp functions throwing errors like [1]. I'm clearly doing something wrong, and must be including the symbol-name package incorrectly? Any pointers would be greatly appreciated? Thanks, Footnotes: [1] USE-PACKAGE #<PACKAGE "PS-DHTML-SYMBOLS"> causes name-conflicts in #<PACKAGE "GPOLYGON"> between the following symbols: #:LENGTH, COMMON-LISP:LENGTH -- Eric Schulte https://cs.unm.edu/~eschulte PGP: 0x614CA05D

1 0

trident-mode.el -- Interactive Parenscript development
by John Mastro 24 Jul '13

24 Jul '13

Hello, I recently started working on an Emacs minor mode with the goal of using SLIME[1] and Skewer[2] to make Parenscript development as dynamic as possible. I'm calling it Trident, and it's online now at https://github.com/johnmastro/trident-mode.el. Skewer, in case you're not familiar with it, allows you to send JavaScript (amongst other things) directly from Emacs to the web browser. Trident's general purpose is to use that ability to treat the browser's JavaScript engine as just another Lisp image that we can send code to for evaluation. Trident also provides commands for displaying the code generated by Parenscript, which can be used without Skewer. If this interests you at all, try it out and let me know what you think. The readme.org at the GitHub repo has more information on setup and usage. I haven't gotten it on ELPA yet but it's a single file and a mere load or require away. Thanks, John Mastro [1] http://common-lisp.net/project/slime/ [2] https://github.com/skeeto/skewer-mode

2 1

(no subject)
by Olaf Ruppert 20 Jul '13

20 Jul '13

1 0

FIX for: CCL isn't happy with ps::warn-deprecated
by Ben Hyde 23 May '13

23 May '13

This code[1] doesn't work well in CCL. Calls upon warn-deprecated play out as so: ps> (warn-deprecated 'forth 'lisp) 0> Calling (warn-deprecated forth lisp) ; Compiler warning: In a toplevel form: Nonspecific warning ; While executing: warn-deprecated, in process repl-thread(12). <0 warn-deprecated returned nil nil ps> This can be resolved by adjusting the condition being defined: ps> (define-condition simple-style-warning (simple-warning style-warning) ()) simple-style-warning ps> (warn-deprecated 'forth 'lisp) 0> Calling (warn-deprecated forth lisp) ; Compiler warning: FORTH is deprecated, use LISP instead ; While executing: warn-deprecated, in process repl-thread(12). <0 warn-deprecated returned nil nil ps> WDYT?

1 0

double floats
by Ben Hyde 06 May '13

06 May '13

Double floats cause issues with the compiler md> (setf *read-default-float-format* 'double-float) double-float md> (ps '(1.0 2.0 3.0)) "[1.0D0, 2.0D0, 3.0D0];" since 1.0D0 isn't javascript This is a simpler example: md> (ps 1.0D0) "1.0D0;" Adding... (defmethod ps-print ((x double-float)) (format *psw-stream* "~F" (coerce x 'single-float))) to printer.lisp resolves the problem. At which point it's tempting to rework the ps-print method on number with: (defmethod ps-print ((x double-float)) (format *psw-stream* "~F" (coerce x 'single-float))) (defmethod ps-print ((x integer)) (format *psw-stream* "~D" x)) (defmethod ps-print ((x number)) (format *psw-stream* "~F" x)) Thanks for this awesome tool! - ben

1 0

[parenscript-devel] Returning (values)
by Robert Monfera 05 Apr '13

05 Apr '13

Hi Guys, (ps (lambda ()(side-effect-call-1)(side-effect-call-2)(side-effect-call-3))) "(function () { sideEffectCall1(); sideEffectCall2(); return sideEffectCall3(); });" (ps (lambda ()(side-effect-call-1)(side-effect-call-2)(side-effect-call-3)(values))) "(function () { sideEffectCall1(); sideEffectCall2(); sideEffectCall3(); __PS_MV_REG = {}; return null; });" What I naively expected is this: "(function () { sideEffectCall1(); sideEffectCall2(); sideEffectCall3(); });" The value of the last subexpression of the lambda expression gets returned by the return statement, which is in line with the intent of the lisp expression. However, the translated version of functions which exist purely for their side effect look weird. I tried to use (values) as the last subexpression, but then it will explicitly return null and set a PS flag in the translated code. A quick search in the doc or the net didn't reveal a good solution. Isn't it desirable to be able to generate lambda expressions that just don't return anything such that it avoids the clutter of additional lines, or am I missing something obvious? Maybe it's to do with the lisp semantics of returning multiple values (including no values), causing (values) not map well to the intuitive version? Thank you, Robert

2 1

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

parenscript-devel