From OpenSimulator

(Difference between revisions)
Jump to: navigation, search
(Multiple script engine usage)
(Multiple script engine usage)
Line 54: Line 54:
Compilers take script text and convert it to a .NET assembly. Such an assembly needs to reference a runtime, which provides API stubs.
This calls out of the appdomain to the API implementation.
Currently, a compiler exists for lsl.
Currently, a compiler exists for lsl, c# and vb. YieldProlog (yp) can be added to c# scripts.
A runtime exists for the LSL API and for the OSSL API. [[LSL Status/Functions]]
The runtime and compiler are not dependent on each other, and also not dependent on the script engine.
The following describes the directory structure(under /OpenSim/Region/):

Revision as of 22:56, 15 November 2018


Script Engines

OpenSimulator supports scripting via script engines. Script engines are normal region modules.

This page deals with common parts of script engines, though OpenSimulator currently only have one public script engine (XEngine). For more information on this, please see XEngine.

For information on the old DotNetEngine which was deprecated in OpenSimulator 0.6.8 and subsequently removed from the core tree, please see DotNetEngine and OpenSim.Region.ScriptEngine.

Note: This page represents an implementation goal. Much of this already works, but some parts are not implemented yet.

OpenSim.ini Settings

Multiple script engines can now be active at once. The script_engine directive in OpenSim.ini is no longer used! Instead, in the [Startup] section, you will now find

DefaultScriptEngine = "XEngine"

XEngine is the default, to change it to any other engine, change the comments to activate the line

DefaultScriptEngine = (some engine name)

XEngine can also be disabled by setting

Enabled = false

These default to true.

OpenSimulator is able to run multiple script engines simultaneously.

Multiple script engine usage

To run a script on a specific engine, begin the script with:

//XEngine: or //(some other engine):

Optionally, this can be followed by a language code:

//(some other engine):c#

Beware: there is a little side effect. If you start your script with anything like

//any text you want:

(starting with "//" and ending with ":") you'll get an error

"Selected engine unavailable. Running script on XEngine"

A script engine defines a way to load and run a script. It uses compilers and runtimes to accomplish this.


Currently, a compiler exists for lsl.

A runtime exists for the LSL API and for the OSSL API. LSL Status/Functions


ScriptEngines/XEngine/ The engine itself. Methods to manage threads, AppDomains, etc
ScriptEngines/Interfaces/ Common interfaces used to create script engines and components
ScriptEngines/Shared/CodeTools/ The currrent compiler
ScriptEngines/Shared/Api/Interface/ The Api interfaces (see below)
ScriptEngines/Shared/Api/Implementation/ The Api implementations (see below)
ScriptEngines/Shared/Api/Runtime/ The Api runtimes (see below)

An API is defined as an implementation, and interface and a runtime. The reason for this seemingly complicated approach has to do with scripts running in AppDomains apart from the normal OpenSimulator code.

Creating an API is pretty straightforward, but a few naming conventions must be observed for the Api to function correctly. The script runtime uses reflection to match Api runtimes to implementations, and it uses names to find these matches.

First, create your API implementation.

namespace OpenSim.Region.ScriptEngine.Shared.Api
     public class XXX_Api: MarshalByRefObject, IXXX_Api, IScriptApi
        internal IScriptEngine m_ScriptEngine;
        internal SceneObjectPart m_host;
        internal uint m_localID;
        internal LLUUID m_itemID;
        public void Initialize(IScriptEngine ScriptEngine, SceneObjectPart host, uint localID, LLUUID itemID)
            m_ScriptEngine = ScriptEngine;
            m_host = host;
            m_localID = localID;
            m_itemID = itemID;
        public void myApiFunction()

Here, the class name (XXX_Api) is used by reflection, it must end in "_Api" to be recognized as an Api.

Place the file in OpenSim/Region/ScriptEngines/Shared/Api/Implementaton/

By convention, it should be named XXX_Api.cs

Next, create an interface to link the Api to the runtime:

namespace OpenSim.Region.ScriptEngine.Shared.Api.Interfaces
     public interface IXXX_Api
         void myApiFunction();

Place this file in OpenSim/Region/ScriptEngines/Api/Interface, named IXXX_Api.

Now, the stub file is needed to connect the script to the Api. This stub file will be loaded into the script AppDomain, and should not contain any processing. It merely forwards the calls to the Api outside of the AppDomain.

namespace OpenSim.Region.ScriptEngine.Shared.ScriptBase
     public partial class ScriptBaseClass : MarshalByRefObject
         public IXXX_Api m_XXX_Functions;
         public void ApiTypeXXX(IScriptApi api)
             if(!(api is IXXX_Api))
             m_XXX_Functions = (IXXX_Api)api;
         public void myApiFunction()

Save this in OpenSim/Region/ScriptEngines/Shared/Api/Runtime, name it XXX_Stub.cs

Here, the ApiTypeXXX naming is the mandatory name, by which the script engine recognizes this Api and matches it up to the API implementation.

Please note that your Api here becomes a part of a partial class, which, in turn, becomes the base class of the script.

On script load, the Api runtime (stub) is called with a reference to the IScriptApi interface of the implementation. That, cast to the custom interface, is used to access the function implementations.

The reason we cannot directly reference the implementation is that that would cause the entire implementation to be loaded into the script's AppDomain. We need to avoid this to keep the memory footprint small.

The directory OpenSim/Region/ScriptEngines/Shared/CodeTools contains all compilers, converters and other code manipulation tools. It is shared between all script engines. Because of the shared compiler, the script engines can also share compiled assemblies, eliminating the need to recompile each script for each script engine.

Code generation

LSL to C# code generation is common to all script engines. This is currently done by translating LSL to C# code and then compiling it. Compiled code then calls methods in LSL_Api.cs (OpenSim/Region/ScriptEngine/Shared/Api/Implementation/LSL_Api.cs) that correspond to LSL functions or methods in OSSL_Api.cs for OSSL functions, etc.

Since OpenSimulator 0.7.4, there is also a mechanism for making script functions available from region modules without patching OpenSimulator itself. See OSSL_Script_Library/ModInvoke for more details.

Parsing the LSL script is kicked off by CSCodeGenerator.Convert() (OpenSim/Region/ScriptEngine/Shared/CodeTools/CSCodeGenerator.cs). This takes the LSL and uses a parser/lexer to convert into in an abstract syntax tree (AST), before then converting that AST to C# via the LSL2CSCodeTransformer.

The parser (lsl.parser.cs) and lexer (lsl.lexer.cs) are generated using Malcolm Crowe's compiler tools in C# from the trunk/managed/lsl2cs directory in the opensim-libs repository from the lsl.parser and lsl.lexer files. Note that if you regenerate this, you will need to change the penultimate number on the arr array in the generated ArgumentDeclarationList_5 class in lsl.parser.cs from 1 to 0. We need to find out why this bug occurs.

The converted C# is then compiled to a DLL by the OpenSimulator Compiler class (via the PerformScriptCompile() method that also triggered LSL -> C# conversion as described above).

You can see the tranformed C# that was compiled by setting

WriteScriptSourceToDebugFile = true

in your OpenSim.ini file. This will appear in the bin/ScriptEngines/<region-id>/ directory with the filename CommonCompiler_source_CommonCompiler_compiled_<script-asset-id>.lsl.

Personal tools
About This Wiki