To follow up on this, the recent patches (specifically ae093417db848a) should now somewhat correctly "expressionize" loops (some work remains on returning actually useful values), and solve this problem.
Vladimir
On Thu, Mar 24, 2011 at 1:06 PM, Daniel Gackle danielgackle@gmail.com wrote:
< Well there's no reason not to wrap it in a lambda >
Do you mean that PS can detect when the LOOP form is being used as an expression and turn it into one with a lambda? That would be great.
I hope you don't mean lambdifying all ordinary vanilla loops, though. That would be not great :)
Dan
On Thu, Mar 24, 2011 at 10:44 AM, Vladimir Sedach vsedach@gmail.com wrote:
Well there's no reason not to wrap it in a lambda, so I'm going to classify this as a bug.
Is there something that can help to convert js code to parenscript code?
Red Daly has https://github.com/gonzojive/js-to-parenscript
Vladimir
parenscript-devel mailing list parenscript-devel@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/parenscript-devel
parenscript-devel mailing list parenscript-devel@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/parenscript-devel