[parenscript-devel] Problem with latest Parenscript

Leslie P. Polzer sky at viridian-project.de
Sun Jan 18 22:10:29 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.

Ah, yes. I got it now. Just making it a non-keyword symbol is
the solution.

Thanks!

-- 
LinkedIn Profile: http://www.linkedin.com/in/polzer
Xing Profile: https://www.xing.com/profile/LeslieP_Polzer
Blog: http://blog.viridian-project.de/





More information about the parenscript-devel mailing list