-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Explore the possibility to use Irony in IronJS #88
Comments
Sprache is also an option that gets a lot of praise. |
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 this would pretty much require us to port the parser / compiler to C# as well. |
Yea, perhaps Sprache is a better fit since it uses Linq instead of operator overloading? |
@otac0n: Have you benchmarked and checked the fact that it's actually the parser that takes up most of the time? |
Well, have a look at these numbers and see if you can determine where we are so much slower: |
I've used Irony for several projects. That thing is a memory hog. I can't see it improving anyone's performance. I really liked Eto.Parse. It was fast. Unfortunately, the author wasn't very interested in providing detailed error output when the parse failed. Someone would have to contribute that. |
Irony is an interesting library for implementing languages on the .NET platform. For its description:
Some effort should be invested into exploring the possibility of using Irony to simplify IronJS.
The text was updated successfully, but these errors were encountered: