[parenscript-devel] Problem with latest Parenscript
After the migration to the git repo of PS this error comes up: The value :|:YAHOO.widget.:Panel| is not of type LIST. Partial backtrace: 13: (SB-PCL::FAST-METHOD PARENSCRIPT::PS-PRINT% ((EQL 'PARENSCRIPT::JS-FUNCALL) T)) Local variables: ARG-3 = (:|:YAHOO.widget.:Panel| ("buddy-manager" (PARENSCRIPT::JS-OBJECT (((PARENSCRIPT::JS-VARIABLE :DRAG-ONLY) (PARENSCRIPT::JS-LITERAL "true")) ((PARENSCRIPT::JS-VARIABLE :CONTEXT) (PARENSCRIPT::ARRAY-LITERAL "header-image" "tr" "tr")) ((PARENSCRIPT::JS-VARIABLE :DRAGGABLE) (PARENSCRIPT::JS-LITERAL "true")) ((PARENSCRIPT::JS-VARIABLE :CLOSEABLE) (PARENSCRIPT::JS-LITERAL "true")))))) Did something change in the symbol handling? Thanks, Leslie -- LinkedIn Profile: http://www.linkedin.com/in/polzer Xing Profile: https://www.xing.com/profile/LeslieP_Polzer Blog: http://blog.viridian-project.de/
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/
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@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@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/parenscript-devel
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/
participants (2)
-
Leslie P. Polzer -
Vladimir Sedach