Georg Holzmann wrote:
Hallo!
note that the library does not have to implement an object of the same name. e.g. there is no [Gem] object in Gem, but you still can load Gem by creating an object [Gem]: the creation will fail but Gem will be loaded.
yes, an other problem is, that e.g. [zexy] has to be created before [nop] ...
that's an important point. [using] should be guaranteed to be called before any other object in the patch. and as you ahve pointed out in your previous mail, having a way to specify the order of [using]s would be nice too.
yes, two things about that:
- this should be local to each abstraction (otherwise reausability of
abstractions is not guaranteed - there could be nameclashes ...)
but hard to do...
- there should also be a way to not load all externs of a lib (like in
python "import nop from zexy" or in C++ "using zexy::nop" ...)
(but I think we already discussed this ...)
that's why it's a zombie.
mfg.adr IOhannes