On 2013-07-04, at 12:52, Torsten Bergmann <astares@gmx.de> wrote:
Usually I thought only the C/C++ people fell in love with abbreviations - but now its our own community:
in Pharo 3.0 one can write:
Smalltalk os env
actually that #env there is more complicated than you think :) - `Smalltalk os` returns OSPlatform, the class - implementing #environment on the class side will break the compiler for this class My first attempt was of course to use #environment as a name, which failed horribly ;) So first we have to complete the refactoring that `Smalltalk os` returns an instance of OSPlatform. Only then we can move to #environment, which by looking at #OSEnvironment is the intended name. So all in all you detected the symptoms of a much worse problem, using class-sides instead of instances. In any case, I agree that #env is not nice at all...