Skip to content
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

Open
asbjornu opened this issue Oct 20, 2011 · 6 comments
Open

Explore the possibility to use Irony in IronJS #88

asbjornu opened this issue Oct 20, 2011 · 6 comments

Comments

@asbjornu
Copy link
Collaborator

Irony is an interesting library for implementing languages on the .NET platform. For its description:

Unlike most existing yacc/lex-style solutions Irony does not employ any scanner or parser code generation from grammar specifications written in a specialized meta-language. In Irony the target language grammar is coded directly in c# using operator overloading to express grammar constructs. Irony's scanner and parser modules use the grammar encoded as c# class to control the parsing process.

Some effort should be invested into exploring the possibility of using Irony to simplify IronJS.

@asbjornu
Copy link
Collaborator Author

Sprache is also an option that gets a lot of praise.

@otac0n
Copy link
Collaborator

otac0n commented Oct 20, 2011

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.

@asbjornu
Copy link
Collaborator Author

Yea, perhaps Sprache is a better fit since it uses Linq instead of operator overloading?

@fholm
Copy link
Owner

fholm commented Oct 20, 2011

@otac0n: Have you benchmarked and checked the fact that it's actually the parser that takes up most of the time?

@fholm fholm closed this as completed Oct 20, 2011
@fholm fholm reopened this Oct 20, 2011
@otac0n
Copy link
Collaborator

otac0n commented Oct 25, 2011

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/

@BrannonKing
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants