Thanks Red. That was enormously embarrassing.<br>Jim<br><br><br><div class="gmail_quote">On Sat, Jun 6, 2009 at 10:00 AM, <span dir="ltr"><<a href="mailto:parenscript-devel-request@common-lisp.net">parenscript-devel-request@common-lisp.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Send parenscript-devel mailing list submissions to<br>
<a href="mailto:parenscript-devel@common-lisp.net">parenscript-devel@common-lisp.net</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://common-lisp.net/cgi-bin/mailman/listinfo/parenscript-devel" target="_blank">http://common-lisp.net/cgi-bin/mailman/listinfo/parenscript-devel</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:parenscript-devel-request@common-lisp.net">parenscript-devel-request@common-lisp.net</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:parenscript-devel-owner@common-lisp.net">parenscript-devel-owner@common-lisp.net</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of parenscript-devel digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Create doesn't create (<a href="mailto:ps_jim@emidium.com">ps_jim@emidium.com</a>)<br>
2. Re: Create doesn't create (Red Daly)<br>
3. Catch forms shouldn't require a variable (Daniel Gackle)<br>
4. Lexical scoping question (Daniel Gackle)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Fri, 05 Jun 2009 12:40:44 -0400<br>
From: <a href="mailto:ps_jim@emidium.com">ps_jim@emidium.com</a><br>
Subject: [parenscript-devel] Create doesn't create<br>
To: <<a href="mailto:parenscript-devel@common-lisp.net">parenscript-devel@common-lisp.net</a>><br>
Message-ID: <16286717.439541244220044718.JavaMail.servlet@perfora><br>
Content-Type: text/plain; charset=UTF-8<br>
<br>
Hey all,<br>
I'm new to parenscript so I hope this is a reasonable question<br>
<br>
I think<br>
<br>
(parenscript:ps (create :foo "bar" :blorg 1))<br>
<br>
should return<br>
<br>
{ foo : 'bar', blorg :1}<br>
<br>
but it returns<br>
<br>
create('foo', 'bar', 'blorg', 1);<br>
<br>
which means it is falling through to a regular function.<br>
<br>
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?<br>
<br>
This was in the last tarball and the latest from git.<br>
<br>
Jim<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Fri, 5 Jun 2009 10:26:14 -0700<br>
From: Red Daly <<a href="mailto:reddaly@gmail.com">reddaly@gmail.com</a>><br>
Subject: Re: [parenscript-devel] Create doesn't create<br>
To: parenscript-devel <<a href="mailto:parenscript-devel@common-lisp.net">parenscript-devel@common-lisp.net</a>><br>
Message-ID:<br>
<<a href="mailto:f6700f0c0906051026o79a5cd35r424ddf9fba2a1c46@mail.gmail.com">f6700f0c0906051026o79a5cd35r424ddf9fba2a1c46@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
Make sure you are using the 'create from the parenscript package:<br>
<br>
(ps:ps (ps:create :foo "bar" :blorg 1))<br>
<br>
that's my guess,<br>
<br>
Red<br>
<br>
On Fri, Jun 5, 2009 at 9:40 AM, <<a href="mailto:ps_jim@emidium.com">ps_jim@emidium.com</a>> wrote:<br>
<br>
> Hey all,<br>
> I'm new to parenscript so I hope this is a reasonable question<br>
><br>
> I think<br>
><br>
> (parenscript:ps (create :foo "bar" :blorg 1))<br>
><br>
> should return<br>
><br>
> { foo : 'bar', blorg :1}<br>
><br>
> but it returns<br>
><br>
> create('foo', 'bar', 'blorg', 1);<br>
><br>
> which means it is falling through to a regular function.<br>
><br>
> I was looking at the source and there create is a 'define-ps-special-form'<br>
> but it's gonna take me a while to figure out what is going on. Any thoughts<br>
> about what I'm doing wrong?<br>
><br>
> This was in the last tarball and the latest from git.<br>
><br>
> Jim<br>
><br>
> _______________________________________________<br>
> parenscript-devel mailing list<br>
> <a href="mailto:parenscript-devel@common-lisp.net">parenscript-devel@common-lisp.net</a><br>
> <a href="http://common-lisp.net/cgi-bin/mailman/listinfo/parenscript-devel" target="_blank">http://common-lisp.net/cgi-bin/mailman/listinfo/parenscript-devel</a><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <a href="http://common-lisp.net/pipermail/parenscript-devel/attachments/20090605/b8cf5627/attachment.html" target="_blank">http://common-lisp.net/pipermail/parenscript-devel/attachments/20090605/b8cf5627/attachment.html</a><br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Fri, 5 Jun 2009 22:54:58 -0600<br>
From: Daniel Gackle <<a href="mailto:danielgackle@gmail.com">danielgackle@gmail.com</a>><br>
Subject: [parenscript-devel] Catch forms shouldn't require a variable<br>
To: parenscript-devel <<a href="mailto:parenscript-devel@common-lisp.net">parenscript-devel@common-lisp.net</a>><br>
Message-ID:<br>
<<a href="mailto:57952f8b0906052154j6d22a87bl6a89061c0efb6cee@mail.gmail.com">57952f8b0906052154j6d22a87bl6a89061c0efb6cee@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
PS throws an error here:<br>
<br>
(ps (try (a) (:catch nil (b))))<br>
<br>
I think it should just gensym an identifier for the catch form. Sometimes<br>
you just want to know whether an error occurred, not what it was.<br>
<br>
This came up because I implemented something like try/catch in CL, for the<br>
code that we compile to both CL and PS. If I stuff a variable in the catch<br>
form, the CL compiler warns about an unused variable. So I wrote a wrapper<br>
to do the above-mentioned gensym thing.<br>
<br>
Daniel<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <a href="http://common-lisp.net/pipermail/parenscript-devel/attachments/20090605/31e4051f/attachment-0001.html" target="_blank">http://common-lisp.net/pipermail/parenscript-devel/attachments/20090605/31e4051f/attachment-0001.html</a><br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Fri, 5 Jun 2009 23:10:18 -0600<br>
From: Daniel Gackle <<a href="mailto:danielgackle@gmail.com">danielgackle@gmail.com</a>><br>
Subject: [parenscript-devel] Lexical scoping question<br>
To: parenscript-devel <<a href="mailto:parenscript-devel@common-lisp.net">parenscript-devel@common-lisp.net</a>><br>
Message-ID:<br>
<<a href="mailto:57952f8b0906052210j7587a0e1l3ca15ad8f3c85836@mail.gmail.com">57952f8b0906052210j7587a0e1l3ca15ad8f3c85836@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
I've played with the recent PS with lexical scoping, and it's grown on me.<br>
My concerns about the readability of gensym'd suffixes are not turning out<br>
to be as bad as I worried, and I'm noticing several benefits to the idea.<br>
I'm hoping the recent batch of bugs we've reported can be fixed so we can<br>
upgrade to the latest.<br>
<br>
In the meantime, I'm trying to understand the intent behind this bit of<br>
language redesign. Consider the following:<br>
<br>
(ps (let ((a 123))<br>
(blah a))<br>
(alert a))<br>
<br>
If this were really lexically scoped, the a in the alert form would be<br>
undefined. But ps generates:<br>
<br>
"var a = 123;<br>
blah(a);<br>
alert(a);"<br>
<br>
Does this reflect what is intended? If so, is there a clear explanation of<br>
just what "lexical scoping" is now offered by PS, i.e. what the rules are,<br>
what we should expect, and what we should not expect?<br>
<br>
Daniel<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <a href="http://common-lisp.net/pipermail/parenscript-devel/attachments/20090605/c2c8fdcc/attachment-0001.htm" target="_blank">http://common-lisp.net/pipermail/parenscript-devel/attachments/20090605/c2c8fdcc/attachment-0001.htm</a><br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
parenscript-devel mailing list<br>
<a href="mailto:parenscript-devel@common-lisp.net">parenscript-devel@common-lisp.net</a><br>
<a href="http://common-lisp.net/cgi-bin/mailman/listinfo/parenscript-devel" target="_blank">http://common-lisp.net/cgi-bin/mailman/listinfo/parenscript-devel</a><br>
<br>
<br>
End of parenscript-devel Digest, Vol 23, Issue 3<br>
************************************************<br>
</blockquote></div><br>