| « The unknown Javascript | ASP.NET Themes » |
Jint - Javascript interpreter for .NET
I have published a new project on codeplex. It's called Jint.
Jint is a script engine based on the Javascript language. Using Jint, developers can provide fully scriptable applications, execute .NET code without compiling, or create external configuration logic, using the most used script language.
Jint aims at providing every JavaScript functionalities to .NET applications, and bindings to .NET languages can be done in both sides. Jint scripts can use any .NET object from your application, and use every part of the .NET base class library.
Enjoy on http://jint.codeplex.com.
Trackback address for this post
6 comments
Comment from: Jb Evain [Visitor] · http://evain.net/blog/
Oh hai Seb.
Why did you chose to implement a pure interpreter instead of re-using, say, the DLR?
Why did you chose to implement a pure interpreter instead of re-using, say, the DLR?
09/22/09 @ 17:12
Comment from: Sébastien Ros [Member] 
Jb, only because you are the only one on earth who is allowed to already use the DLR in his developments ;). This implementation can work on any version of the framework. But one day, it will be deprecated, I know.
09/22/09 @ 17:30
Comment from: Jb Evain [Visitor] · http://evain.net/blog/
That's one perfectly valid reason. I was just being curious :)
That being said, it should not be too hard to write a visitor transforming your own AST into a DLR AST.
That being said, it should not be too hard to write a visitor transforming your own AST into a DLR AST.
09/22/09 @ 17:47
Comment from: Bertrand Le Roy [Visitor] · http://weblogs.asp.net/bleroy
Yum! I have a couple of very good use cases for this once it's completed...
09/22/09 @ 20:40
Comment from: Sébastien Ros [Member]
@Jb
First doesn't it already exist with JScript.NET ? Or did they forget to implement the DLR version of it ? Secondly, convince me. What advantages/innovation to go to DLR also ?
First doesn't it already exist with JScript.NET ? Or did they forget to implement the DLR version of it ? Secondly, convince me. What advantages/innovation to go to DLR also ?
09/22/09 @ 22:53
Comment from: Jb Evain [Visitor] · http://evain.net/blog/
JScript.NET is basically old, deprecated, and has never been updated since .net 1.1. Doesn't really sounds like a good choice.
AFAIK, there's no plan to have a DLR based jscript in .net 4.0.
They do have one though, that used to ship with the early betas of Silverlight, but it's nowhere to be found nowadays.
For heavy usages, you'd get a performance boost. That being said, both IPY and IR have transitioned to a mixed interpreter / compiler state, where only the code called often gets compiled.
You could get debuggability of the scripts. Also you'd get interop with the other DLR based languages, or languages that support it. For instance you could have a «dynamic» C#4 object talking «natively» to a Jint object.
AFAIK, there's no plan to have a DLR based jscript in .net 4.0.
They do have one though, that used to ship with the early betas of Silverlight, but it's nowhere to be found nowadays.
For heavy usages, you'd get a performance boost. That being said, both IPY and IR have transitioned to a mixed interpreter / compiler state, where only the code called often gets compiled.
You could get debuggability of the scripts. Also you'd get interop with the other DLR based languages, or languages that support it. For instance you could have a «dynamic» C#4 object talking «natively» to a Jint object.
09/23/09 @ 08:40
Comment feed for this post