That said, I just ran an exported c2runtime.js through JSLint (via Notepad++) and it had nearly no issues. The following illustrates one such issue.
Here's a portion of the original exported code:
<img src="http://dl.dropbox.com/u/41325628/construct2/jslint/c2_conditionals.jpg" border="0" />
And here's an adjusted version that passes JSLint:
<img src="http://dl.dropbox.com/u/41325628/construct2/jslint/c2_conditionals_alternate.jpg" border="0" />
Just that small change in the structure allows that one item to pass through JSLint. And with that adjustment, there were only a few small issues left over, as illustrated in the following:
<img src="http://dl.dropbox.com/u/41325628/construct2/jslint/c2_jslint.jpg" border="0" />
Of course, I'm not expecting changes to be made to C2 to accommodate JSLint. I was just thinking that since it's so very close to passing JSLint inspection, it'd be a pretty nice thing to be able to advertise that it does so.