parenscript-devel June 2009

parenscript-devel@common-lisp.net

6 participants
9 discussions

[parenscript-devel] long compile time
by Kelly McDonald 06 Jul '09

06 Jul '09

Hello, I'm sure I'm doing something dumb, I just need someone to set me straight. I recently updated to the latest parenscript (as well as sbcl) and got all of the errors for where I had this.dropdownlist.length type notation and changed it to (@ this dropdownlist length) notation. I had something that used to compile rather quickly it was as simple as this: (defun somefunction () (ps (very long parenscript code))) if I evaluate just the (ps (very long parenscript code)) everything is really snappy & I get what I expect. if I evaluate the whole function, it takes forever (ok, like 10 minutes) again, once things evaluate, I get what I expect Furthermore, if I start small and add stuff in, it seems to take exponential time to the amount of code (or more likely my patience gets exponentially shorter) the same thing happens if I merely do a (setf somevar (ps (very long parenscript code))) I'm suspecting that I'm hitting some kind of compiler optimization and I need some kind of pragma. Thanks for your thoughts/suggestions, Kelly McDonald

2 3

[parenscript-devel] Lexical scoping question
by Daniel Gackle 08 Jun '09

08 Jun '09

I've played with the recent PS with lexical scoping, and it's grown on me. My concerns about the readability of gensym'd suffixes are not turning out to be as bad as I worried, and I'm noticing several benefits to the idea. I'm hoping the recent batch of bugs we've reported can be fixed so we can upgrade to the latest. In the meantime, I'm trying to understand the intent behind this bit of language redesign. Consider the following: (ps (let ((a 123)) (blah a)) (alert a)) If this were really lexically scoped, the a in the alert form would be undefined. But ps generates: "var a = 123; blah(a); alert(a);" Does this reflect what is intended? If so, is there a clear explanation of just what "lexical scoping" is now offered by PS, i.e. what the rules are, what we should expect, and what we should not expect? Daniel

3 3

[parenscript-devel] APPLY with FLET/LABELS
by sblist＠me.com 08 Jun '09

08 Jun '09

Good morning, FLET and LABELS appears not to work with APPLY. Using regular function application or FUNCALL, the gensymed symbol is used: PS> (flet ((foo () 'bar)) (foo)) BAR PS> (ps (flet ((foo () 'bar)) (foo))) "var foo1 = function () { 'bar'; }; foo1();" PS> (ps (flet ((foo () 'bar)) (funcall foo))) "var foo3 = function () { 'bar'; }; foo3();" PS> APPLY, however, does not use the gensym: PS> (ps (flet ((foo () 'bar)) (apply foo nil))) "var foo2 = function () { 'bar'; }; foo.apply(this, null);" - Scott

2 2

[parenscript-devel] DESTRUCTURING-BIND broken with parallel LET
by sblist＠me.com 08 Jun '09

08 Jun '09

DESTRUCTURING-BIND relies on sequential evaluation in its generated bindings, so must be updated to use LET*: diff --git a/src/lib/ps-macro-lib.lisp b/src/lib/ps-macro-lib.lisp index cb413cf..5c65ad6 100644 --- a/src/lib/ps-macro-lib.lisp +++ b/src/lib/ps-macro-lib.lisp @@ -146,4 +146,4 @@ (mapcan (lambda (var) (incf n) (when var `((,var (aref ,arr ,n))))) vars)))) - `(let ,bindings ,@body))) + `(let* ,bindings ,@body))) - Scott

2 1

[parenscript-devel] Macro symbols affect GENSYMing in LET
by sblist＠me.com 08 Jun '09

08 Jun '09

I haven't done a very good job of distilling down this bug, but we're experiencing an issue with the GENSYMing done by LET in the presence of macros with the same names as variables bound in LET. This is the simplest example I could come up with: > (ps (macrolet ((a (n) `(+ ,n 5))) (let ((a (a 1))) (let ((b (a (- a 4)))) (+ a b))))) "var a1661 = 1 + 5; var b = (a - 4) + 5; a1661 + b;" You can see here that the symbol A is GENSYM'd since it occurs elsewhere in the LET binding forms, but it seems to be missed in the inner LET form. If the symbol A is not inside the subtraction form, it is caught: > (ps (macrolet ((a (n) `(+ ,n 5))) (let ((a (a 1))) (let ((b (a a))) (+ a b))))) "var a1662 = 1 + 5; var b = a1662 + 5; a1662 + b;" - Scott

2 2

[parenscript-devel] FLATTEN no longer supports dotted lists
by sblist＠me.com 08 Jun '09

08 Jun '09

Hi folks, We have some code that fails during ps-macroexpansion time as a result of the following change in src/utils.lisp: Previous definition (works): (defun flatten (x &optional acc) (cond ((null x) acc) ((atom x) (cons x acc)) (t (flatten (car x) (flatten (cdr x) acc))))) Current definition (crashes): (defun flatten (x) (if (atom x) (list x) (mapcan #'flatten x))) The failing call in the backtrace is (FLATTEN (IE . 6)), with a type error: 6 is not of type LIST. This is expected, given that current definition of FLATTEN calls MAPCAN. FLATTEN is only being called when the PS macro that fails to expand, BROWSER-CASE, is wrapped in a LET form: > (ps (browser-case '(:ie . 6) 'foo :default 'bar)) "'bar';" > (ps (let ((baz (browser-case '(:ie . 6) 'foo :default 'bar))) baz)) ; Evaluation aborted. (Failure) - Scott

2 1

Re: [parenscript-devel] Create doesn't create
by Jim McDonald 06 Jun '09

06 Jun '09

Thanks Red. That was enormously embarrassing. Jim On Sat, Jun 6, 2009 at 10:00 AM, <parenscript-devel-request(a)common-lisp.net>wrote: > Send parenscript-devel mailing list submissions to > parenscript-devel(a)common-lisp.net > > To subscribe or unsubscribe via the World Wide Web, visit > http://common-lisp.net/cgi-bin/mailman/listinfo/parenscript-devel > or, via email, send a message with subject or body 'help' to > parenscript-devel-request(a)common-lisp.net > > You can reach the person managing the list at > parenscript-devel-owner(a)common-lisp.net > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of parenscript-devel digest..." > > > Today's Topics: > > 1. Create doesn't create (ps_jim(a)emidium.com) > 2. Re: Create doesn't create (Red Daly) > 3. Catch forms shouldn't require a variable (Daniel Gackle) > 4. Lexical scoping question (Daniel Gackle) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 05 Jun 2009 12:40:44 -0400 > From: ps_jim(a)emidium.com > Subject: [parenscript-devel] Create doesn't create > To: <parenscript-devel(a)common-lisp.net> > Message-ID: <16286717.439541244220044718.JavaMail.servlet@perfora> > Content-Type: text/plain; charset=UTF-8 > > Hey all, > I'm new to parenscript so I hope this is a reasonable question > > I think > > (parenscript:ps (create :foo "bar" :blorg 1)) > > should return > > { foo : 'bar', blorg :1} > > but it returns > > create('foo', 'bar', 'blorg', 1); > > which means it is falling through to a regular function. > > I was looking at the source and there create is a 'define-ps-special-form' > but it's gonna take me a while to figure out what is going on. Any thoughts > about what I'm doing wrong? > > This was in the last tarball and the latest from git. > > Jim > > > > ------------------------------ > > Message: 2 > Date: Fri, 5 Jun 2009 10:26:14 -0700 > From: Red Daly <reddaly(a)gmail.com> > Subject: Re: [parenscript-devel] Create doesn't create > To: parenscript-devel <parenscript-devel(a)common-lisp.net> > Message-ID: > <f6700f0c0906051026o79a5cd35r424ddf9fba2a1c46(a)mail.gmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > Make sure you are using the 'create from the parenscript package: > > (ps:ps (ps:create :foo "bar" :blorg 1)) > > that's my guess, > > Red > > On Fri, Jun 5, 2009 at 9:40 AM, <ps_jim(a)emidium.com> wrote: > > > Hey all, > > I'm new to parenscript so I hope this is a reasonable question > > > > I think > > > > (parenscript:ps (create :foo "bar" :blorg 1)) > > > > should return > > > > { foo : 'bar', blorg :1} > > > > but it returns > > > > create('foo', 'bar', 'blorg', 1); > > > > which means it is falling through to a regular function. > > > > I was looking at the source and there create is a > 'define-ps-special-form' > > but it's gonna take me a while to figure out what is going on. Any > thoughts > > about what I'm doing wrong? > > > > This was in the last tarball and the latest from git. > > > > Jim > > > > _______________________________________________ > > parenscript-devel mailing list > > parenscript-devel(a)common-lisp.net > > http://common-lisp.net/cgi-bin/mailman/listinfo/parenscript-devel > > >

1 0

[parenscript-devel] Catch forms shouldn't require a variable
by Daniel Gackle 06 Jun '09

06 Jun '09

PS throws an error here: (ps (try (a) (:catch nil (b)))) I think it should just gensym an identifier for the catch form. Sometimes you just want to know whether an error occurred, not what it was. This came up because I implemented something like try/catch in CL, for the code that we compile to both CL and PS. If I stuff a variable in the catch form, the CL compiler warns about an unused variable. So I wrote a wrapper to do the above-mentioned gensym thing. Daniel

1 0

[parenscript-devel] Create doesn't create
by ps_jim＠emidium.com 05 Jun '09

05 Jun '09

Hey all, I'm new to parenscript so I hope this is a reasonable question I think (parenscript:ps (create :foo "bar" :blorg 1)) should return { foo : 'bar', blorg :1} but it returns create('foo', 'bar', 'blorg', 1); which means it is falling through to a regular function. I was looking at the source and there create is a 'define-ps-special-form' but it's gonna take me a while to figure out what is going on. Any thoughts about what I'm doing wrong? This was in the last tarball and the latest from git. Jim

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

parenscript-devel June 2009