Original Post
Hi, I'm currently designing a scripting language, mostly for learning purposes, which will run under a virtual machine. Now, there is one thing I don't know how to solve - standard library (and other libraries, for that matter). I could implement various functions as 'keywords', that is, make the vm aware of them, and probably provide direct assembler instructions for each of them(since it's a custom-made assembler, used only by vm). But that doesn't really provide much flexibility - each time I want to add a function to the language, I need to change the asm and vm, and the language keyword list grows unacceptably large... Is there a standard way of doing this? Perhaps providing some mechanism of connecting .dll/.so to to the scripting language, so that new libraries can be written in a 'standard' language, and then simply imported to the script? Or can this be done in a simpler way? Thanks, -Ivan