Igor Stasenko wrote
I think that we missing a way to determine to which package some global belongs to. When you loading a package it can declare new global, but there is no reflective mechanisms in system to tell, to which package it belongs. If we could have that, then clearly, if you serialize the package, you would want to serialize its globals as well, and if not, you can just leave a reference to it, which will be rewired at materialization.
For what is worth and as reference, Dolphin Smalltalk packages includes a list of globals that belong to it Davorin Rusevljan ----- http://www.cloud208.com/ -- View this message in context: http://forum.world.st/How-to-globals-that-are-NOT-classes-or-traits-tp456435... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.