Scripting Language extensions via plugins

[enlight_2014]

@;98169

That makes sense, sure. I originally thought that there’s going to be multiple plugins that support a specific language and this one could be used as a template once it matures (because I imagine that each integration would like to add specific functionality to it). However, I guess it could be possible to dynamically support different language contexts and have the engine -> script glue (class compiler etc) be only one. I’ll look into it.

To date I’ve had to make a few changes to ScriptPlugin, and now I’m going to move all those changes into a separate plugin. Which is to say, you were right about this set of plugins being just a template.