Hi guys. Thanks for the character information. Works great.
I'm now playing with jslint running in rhino and it seems like it gives some pretty useful information.
The one thing it is mentioning above all others is the presence of unnecessary semicolons after function definitions after brackets. I'm wondering what your thoughts would be If I dig in and try and remove these?
Will
That's a really good idea; getting Parenscript to generate code that passes all the reasonable JSLint checks is something I also want to do.
As an aside, I have also been considering the idea of doing a JavaScript implementation in CL, both to write more effective tests for Parenscript, and to provide the option to run JSLint on the output to generate compiler warnings (and of course to provide a JS interpreter to things like the Closure web browser). Adding analysis to PS itself is another want. In the meantime, I think I'll try to prototype JSLint checking by making an HTTP request to jslint.com and see what the best way to provide feedback is.
Vladimir
On Sun, Mar 1, 2009 at 11:41 AM, William Halliburton whalliburton@gmail.com wrote:
Hi guys. Thanks for the character information. Works great.
I'm now playing with jslint running in rhino and it seems like it gives some pretty useful information.
The one thing it is mentioning above all others is the presence of unnecessary semicolons after function definitions after brackets. I'm wondering what your thoughts would be If I dig in and try and remove these?
Will
parenscript-devel mailing list parenscript-devel@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/parenscript-devel
As an aside, I have also been considering the idea of doing a JavaScript implementation in CL, both to write more effective tests for Parenscript, and to provide the option to run JSLint on the output to generate compiler warnings (and of course to provide a JS interpreter to things like the Closure web browser).
Wow, that's ambitious. Sound like fun, too, but lots of work. Might be much easier to create a foreign interface to spidermonkey, which seems like a pretty strightforward c library. Not lisp, but might be an easy win.
Adding analysis to PS itself is another want.
What types of analysis are you thinking about?
parenscript-devel@common-lisp.net
-
Vladimir Sedach -
William Halliburton