email@example.com (RT Happe) writes:
>> But for this case none of these are a good solution, because neither I
>> want to execute this interactively, nor are these test modules
>> executables by themselves. I need to programmatically load the configure
>> package definitions to define new structures in modules that aren't
>> executable scripts by themselves, but libraries of functions.
> In a typical situation, you specify module dependencies statically in a
> configuration file, load that in the config package as Mike Sperber
> indicated, and let the scsh system do the loading of required files
> whenever you open a structure, e.g. a structure test-suite that exports
> the binding run-tests and depends on other structures test-foo, test-bar,
> scsh, whatever. I don't see why this shouldn't fit your needs. Anyway,
> you may want to read up on Scheme 48 modules (much different from the
> old-style provide/require mechanism) and have a look on Olin Shivers
> explanation listed in the docu section at scsh.net:
But would it be possible to dynamically instantiate test cases?
For example, in Java you could have a test interface. The main
program would then instantiate a class implementing the test interface
from each file in a file system directory (I believe this falls under
reflection). This way the specific test cases are not hard-wired into
the main program.
Could this be done with S48 modules? Am I comparing apples with
oranges? What would the correct way be to achieve this?