first fully working version of THREE.Ray with local system\n this is already lots of times better then the previous version but is still not very optimized

Added this.range parameter. Range check could be done manually afterwards. But when interested if multiple projectiles (=rays) hit a moving mesh, a lot of time is wasted on checking the mesh faces should the mesh still be out of range. If no range is specified, behaviour remains the same.

(Phewww!) I'm sure there are still things I missed...

Updated Closure compiler. Added more verbose compile warnings. Fixed all compile warnings. Started to fix runtime warnings in examples.

For verbose compile warnings to be practical I had to add externs and disable some warnings manually (there were tons of complains about "global this" and "cannot instantiate non-constructor"). Other solution would be to annotate explicitly constructors all over the code base.

(prompted by John Carmack's praise of static code analysis http://altdevblogaday.com/2011/12/24/static-code-analysis/)

And still readable code...

It's enough to clone just for hits, no need to do it for every face.

Removed some clone() calls while still keeping the code somewhat pretty.