Re: OOC Package Tool: Repositories

[hartmut Goebel <hartmut@oberon.noris.de>]

Michael van Acken (acken@vanacken.do.uunet.de) schrieb:

 >The Oberon-style of dynamic loading only provides dynamic access to a
 >single kind of resource: parameterless procedures that are exported by
 >the loaded module.

This is not fully correct, since dynamic loading and access to resources are
seperate issues!

In the Oberon System(s) dynamic loading is used for a couple of purposes, eg.
for the "commands" you mentioned. Further important usage is for loading
"elements" (dynamic content for texts).

 >To get the full range of meta-programming it makes sense to slurp the
 >symbol file into the program during run-time.  This way the whole

Sorry, I have to disagree here: for "the full rang of meta-programming" one
does not only need information about the interface, but much more important
information about _all_ procedures and variables.

 >This would even work with oo2c.

As we discussed earlier, implementing "Ref" is not possible with oo2c :-(

 >After array descriptors have been added to the run-time environment,
 >all program data (excluding the procedure stack) can be accessed
  ^^^^^^^^^^^
 >through a `Ref'-like library module.

In no way corect, sorry (accourting to what you wrote above). You'll still
miss global, non-exported vars.

NB: trying to implement "Ref" without full access to local variables, too, is
simply worthless: you'll loose a big part of it's functionality.

+++hartmut