We are assuming two executional models of usage:
C-SMILE runtime (exe version) as top-level controller with dynamic loading of user defined modules - DLLs (c-smile-native-interface) and csp(source packages) or cse(bytecodes).
C-SMILE as a scripting engine (e.g. DLL) embedded in someone's application. Internal application's objects, wrapped in C-SMILE classes, are being injected in C-SMILE namespace during engine initialization (or dynamically at runtime).
andrew@terra-informatica.org
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
We are assuming two executional models of usage:
C-SMILE runtime (exe version) as top-level controller with dynamic loading of user defined modules - DLLs (c-smile-native-interface) and csp(source packages) or cse(bytecodes).
C-SMILE as a scripting engine (e.g. DLL) embedded in someone's application. Internal application's objects, wrapped in C-SMILE classes, are being injected in C-SMILE namespace during engine initialization (or dynamically at runtime).
andrew@terra-informatica.org