> - A setting with value is an instance of SettingValue or of one of its > subclasses. Such a setting holds a useful global system parameter and > is made persistent: it is stored in a class variable which is > initialized by the method that declares the setting.
I think the problem with this proposal is that it mixes the model (the value of the setting) and the meta-model (the model of the setting). This is problematic because then all code depends on the settings package and when reading/writing settings application code must be aware of the indirection introduced through the setting. Why isn't a setting simply a variable local to the package, and the setting-description a separate object (method) that can also be packaged separately? Lukas -- Lukas Renggli http://www.lukas-renggli.ch _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
