Neil wrote: > This is OK for those with access to the scripts. > I am working in VB, on Windows, and may not be able to make > use of software which is not compatible. This was because the > program was ported from QBasic. > There is no way in which I could ever rewrite 100k lines of > code now.
That's exactly why I suggested using an embeddable scripting language. The interpreter cames as a dll and your program just call the appropriate functions. The core of our "abc subsystem" (please, someone suggest a name for this "thing") could be released as a library (a dll under Win32) that can be called from whatever dll-capable language (VB included). After adding the appropriate definitions in your VB code, you simply call some function like abcOpen() that will give you back the handle you will use when calling abcTranspose() or abcGetVoice() (just dreaming, a lot of work should be done on the API side). Of course executables for command line interface will also be provided. The core scripts may reside in a separate directory or even being precompiled and stored in the dll itself (for example for providing "default" behaviours). Since you want to "embed" the system in your application, you are free to decide where those script should be placed. The "command line" version will have the appropriate configuration file to be able to access the scripts. Apart from the basic abc functions is up to you which part of your 100k lines makes more sense to move to scripts or rewrite to take advantage of the new functions available. Do you see any other major obstacle to this approach? To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
