Javascript Interpreter for C# (no dependencies)
#scripting #script-engine

Marko Lahma c9531c3a59 upgrade Esprima and BenchmarkDotNet (#468) 7 年之前
Jint c9531c3a59 upgrade Esprima and BenchmarkDotNet (#468) 7 年之前
Jint.Benchmark c9531c3a59 upgrade Esprima and BenchmarkDotNet (#468) 7 年之前
Jint.Repl 75b605f826 Fixing unit tests 7 年之前
Jint.Tests e0d2e2f244 Introduce JsString, JsBoolean etc and support efficient string concatenation (#463) 7 年之前
Jint.Tests.CommonScripts e0d2e2f244 Introduce JsString, JsBoolean etc and support efficient string concatenation (#463) 7 年之前
Jint.Tests.Ecma e0d2e2f244 Introduce JsString, JsBoolean etc and support efficient string concatenation (#463) 7 年之前
.gitattributes f370637777 Ignoring javascript files for language detection 8 年之前
.gitignore 189af9f321 Make ObjectInstance MruPropertyCache2 dictionary lazy (#454) 7 年之前
CREDITS.txt 5f713ad215 Using FastDtoa to serialize numbers 11 年之前
Common.props 03e614b6c9 Generating file version 8 年之前
Jint.sln f6115b2c42 wip 8 年之前
Jint.sln.DotSettings 478662033e Refactoring Date to reflect specifications 11 年之前
LICENSE.txt f53137698a Adding license information 11 年之前
NuGet.config 75b605f826 Fixing unit tests 7 年之前
README.md e7741ed574 Fix myget badge 8 年之前
appveyor.yml d09f109015 Automatic deployments for 3.0-beta on Nuget 7 年之前

README.md

Build status NuGet MyGet

Jint

Jint is a Javascript interpreter for .NET which provides full ECMA 5.1 compliance and can run on any .NET platform. Because it doesn't generate any .NET bytecode nor use the DLR it runs relatively small scripts faster. It's available as a PCL on Nuget at https://www.nuget.org/packages/Jint.

Features

ECMAScript 6.0 currently being implemeted, see https://github.com/sebastienros/jint/issues/343

Discussion

Join the chat on Gitter or post your questions with the jint tag on stackoverflow.

Examples

This example defines a new value named log pointing to Console.WriteLine, then executes a script calling log('Hello World!').

    var engine = new Engine()
        .SetValue("log", new Action<object>(Console.WriteLine))
        ;
    
    engine.Execute(@"
      function hello() { 
        log('Hello World');
      };
      
      hello();
    ");

Here, the variable x is set to 3 and x * x is executed in JavaScript. The result is returned to .NET directly, in this case as a double value 9.

    var square = new Engine()
        .SetValue("x", 3) // define a new variable
        .Execute("x * x") // execute a statement
        .GetCompletionValue() // get the latest statement completion value
        .ToObject() // converts the value to .NET
        ;

You can also directly pass POCOs or anonymous objects and use them from JavaScript. In this example for instance a new Person instance is manipulated from JavaScript.

    var p = new Person {
        Name = "Mickey Mouse"
    };

    var engine = new Engine()
        .SetValue("p", p)
        .Execute("p.Name === 'Mickey Mouse'")
        ;

You can invoke JavaScript function reference

    var add = new Engine()
        .Execute("function add(a, b) { return a + b; }")
        .GetValue("add")
        ;

    add.Invoke(1, 2); // -> 3

or directly by name

    var engine = new Engine()
        .Execute("function add(a, b) { return a + b; }")
        ;

    engine.Invoke("add", 1, 2); // -> 3

Accessing .NET assemblies and classes

You can allow an engine to access any .NET class by configuring the engine instance like this:

    var engine = new Engine(cfg => cfg.AllowClr());

Then you have access to the System namespace as a global value. Here is how it's used in the context on the command line utility:

    jint> var file = new System.IO.StreamWriter('log.txt');
    jint> file.WriteLine('Hello World !');
    jint> file.Dispose();

And even create shortcuts to common .NET methods

    jint> var log = System.Console.WriteLine;
    jint> log('Hello World !');
    => "Hello World !"

When allowing the CLR, you can optionally pass custom assemblies to load types from.

    var engine = new Engine(cfg => cfg
        .AllowClr(typeof(Bar).Assembly)
    );

and then to assign local namespaces the same way System does it for you, use importNamespace

    jint> var Foo = importNamespace('Foo');
    jint> var bar = new Foo.Bar();
    jint> log(bar.ToString());

adding a specific CLR type reference can be done like this

engine.SetValue("TheType", TypeReference.CreateTypeReference(engine, typeof(TheType)))

and used this way

    jint> var o = new TheType();

Generic types are also supported. Here is how to declare, instantiate and use a List<string>:

    jint> var ListOfString = System.Collections.Generic.List(System.String);
    jint> var list = new ListOfString();
    jint> list.Add('foo');
    jint> list.Add(1); // automatically converted to String
    jint> list.Count; // 2

Internationalization

You can enforce what Time Zone or Culture the engine should use when locale JavaScript methods are used if you don't want to use the computer's default values.

This example forces the Time Zone to Pacific Standard Time.

    var PST = TimeZoneInfo.FindSystemTimeZoneById("Pacific Standard Time");
    var engine = new Engine(cfg => cfg.LocalTimeZone(PST));
    
    engine.Execute("new Date().toString()"); // Wed Dec 31 1969 16:00:00 GMT-08:00

This example is using French as the default culture.

    var FR = CultureInfo.GetCultureInfo("fr-FR");
    var engine = new Engine(cfg => cfg.Culture(FR));
    
    engine.Execute("new Number(1.23).toString()"); // 1.23
    engine.Execute("new Number(1.23).toLocaleString()"); // 1,23

Implemented features:

  • ECMAScript 5.1 test suite (http://test262.ecmascript.org/)
  • Manipulate CLR objects from JavaScript, including:
    • Single values
    • Objects
    • Properties
    • Methods
    • Delegates
    • Anonymous objects
  • Convert JavaScript values to CLR objects
    • Primitive values
    • Object -> expando objects (IDictionary<string, object> and dynamic)
    • Array -> object[]
    • Date -> DateTime
    • number -> double
    • string -> string
    • boolean -> bool
    • Regex -> RegExp
    • Function -> Delegate

Continuous Integration kindly provided by AppVeyor