[parenscript-devel] Problem with latest Parenscript

Vladimir Sedach vsedach at gmail.com
Sun Jan 18 16:35:38 UTC 2009


Oh yes, that's it. Is there a special reason to use keywords as
function names in your code? As the commit message states, that was a
behavior of PS that was inconsistent with the way CL treats keywords,
so I decided to change it.

Vladimir

On Sun, Jan 18, 2009 at 4:40 AM, Leslie P. Polzer
<sky at viridian-project.de> wrote:
>
>>   The value :|:YAHOO.widget.:Panel| is not of type LIST.
>>
>> Did something change in the symbol handling?
>
> Evidence suggests that the additional COND case introduced
> in f2bb932ef8 (file src/compiler.lisp, fn compile-parenscript-form)
> breaks handling of symbols like the above.
>
>  Leslie
>
> --
> LinkedIn Profile: http://www.linkedin.com/in/polzer
> Xing Profile: https://www.xing.com/profile/LeslieP_Polzer
> Blog: http://blog.viridian-project.de/
>
>
> _______________________________________________
> parenscript-devel mailing list
> parenscript-devel at common-lisp.net
> http://common-lisp.net/cgi-bin/mailman/listinfo/parenscript-devel
>




More information about the parenscript-devel mailing list