What would be design of a possible solution?
With a different class creation it would be possible
Color subclass: #TranslucentColor
instanceVariables: 'alph';
annotation: #deprecated.
nothing prevent us to design something, this is just that we are stuck
in the past :)
Stef
On 15/9/14 21:58, Torsten Bergmann wrote:
Currently only methods support pragmas in Pharo. Therefore we already had a
discussion
about "Pragmas/Annotations for classes". See
http://forum.world.st/Pragmas-Annotations-for-classes-td2282310.html
To summarize: it would be helpfull to have them (and with them also get rid of
workarounds
like specific conventions, abusing class comments, etc.).
At that time it was not possible to add an iVar to Class, but this issue
was solved already:
https://pharo.fogbugz.com/f/cases/11596/Adding-an-iVar-to-class-Class-gives-error
Must admit I havent tested in latest Pharo 4 if this is still working.
After we now have slots and other nice extensions in Pharo again my basic
question: what about having "annotations" for a class in Pharo. I think we will
find enough use cases on annotating a class with someting useful. Even a
category
or a comment could just be an annotation.
Is there interest to have such a change for Pharo4 or are there reasons to
abandon such
an idea. I guess such a change could not be provided with a simple slice. Any
thoughts/decisions?
Thanks
T.
