Fredrik Holmström
Fredrik Holmström
We'll make sure to open up the IronJS.Compiler.Parser for external use, the reason it's been kept internal is that the API is a bit crufty and not finalized (there's a...
@otac0n: Have you benchmarked and checked the fact that it's actually the parser that takes up most of the time?
They are referenced for the .NET 2.0 build, they must have been included by mistake in the .NET 4.0 project files. * Regards, Fredrik Holmström* On Mon, Oct 15, 2012...
Thanks for reporting this, adding it to the 0.2.1 milestone
1) is fixed in commit [7c9f57e84](https://github.com/fholm/IronJS/commit/7c9f57e849e8a23d3d41102ae14879b4487a9e76)
We're working on improving the line/column reporting, it's pretty bad no doubt, it'll get a lot better. _It's also a requirement for the planned integrated VS debugging_
@ChaosPandion: We have to use this struct because of the performance implications of using a tagged union,this struct is the fastest possible way to do dynamic typing within the DLR
I agree, this is priority #1 in the ES5 spec as it has some type of effect on pretty much everything else in the whole engine.
I will start working on this over the weekend.
I've been forgetting to update the build-script as we've been making progress on the windows side, going to get my Ubuntu dual boot up and running again and make sure...