John Gietzen

Well, we do need to rewrite the parser, I believe. It seems that that is our current performance bottleneck. Irony is made or use with C# operator overloading, and so...

Well, have a look at these numbers and see if you can determine where we are so much slower: http://blog.excastle.com/2011/10/16/net-and-coffeescript-comparing-jurassic-jint-and-ironjs/

We'll take a look.

We have to return `object`, in order to support dynamic interop. The easiest thing to do is just use `dynamic a = Execute(...);` and do your thing with the `a`...

I'm not sure that this is the best way to support AnyCPU. Rather, I think that we should change the order of the field offests, and make the value types...

I would absolutely love to get away from separate X86 and X64 builds, if that is possible, but I have to defer to Fredrik on this one, since I don't...

@fholm: Are my changes feasible? I'm running the tests right now, but I cant test for regressions, since I hadn't run the tests before on this machine. (And, I have...

(Sorry, Github auto-closed the issue.) I have run the Sputnik tests, and there were no regressions. I have also reconfigured the solution and project files to reflect the unified processor...

@jlarsson, we have made the update. I have also pushed it to NuGet! Whee!

Can you confirm whether this fixes your issue?