Typed array browsers passes the test, but... we're passing around a different NaN value for NaN operations. JavaScript's NaN value is almost identical to Java's, but has the sign bit set.

I'm currently dealing with this subtlety, and another subtle infinity-related bug. I have changed the code so that float infinities map to JavaScript's infinities, but I think there's at least one case where this is not the case. Still tracking that down...

So, more progress toward #128.
Committing this test before I back out some of the complex NaN logic that I no longer care about. It's not really in the spec.
Float NaN behavior finally appears to work correctly with and without typed arrays. :)

Now on to doubles!
Floats don't need that extra logic anymore since we use JavaScript NaNs. :)
DoubleMath NaN and infinity tests!
I believe I have finished #128. Just need to finish a few tests of double<->long conversions.
Alright, I'm satisfied with our double<->long conversions. Closing #128.
For #39, I have done the following changes:

* Changed instances of Number.isNaN to just isNaN.
* Changed console.log.apply to just console.log with the array input joined together. It's cleaner.

I also changed an instance of DoppioVM to Doppio.
RawMemory passes in IE9! This should fix #39.
show diffs when not in 'all' mode, per #126
Fixing FloatMath in Opera. Opera has a different standard NaN value than Java, so let's not care about what its int representation is.
return exceptions should never escape to  run_until_finished
Changing array_to_bytestr so that we don't call .apply on String.fromCharCode. This fixes #129.
Merge branch 'master' of https://github.com/int3/doppio
updating comment for array_to_bytestr
removing unused thread cruft
adding ReturnException back in, temporarily

we don't yet have a way of testing behavior on classpath failure, or
wrong name errors, etc
fixing typo
updating code samples
fixing makefile for doc generation / make dist