hi
deprecating methods is simple and works well. Now I'm wondering how we could deprecate classes? Let them in the image in a special categoriy and redefining basicNew to use the same deprecation mechanism? Any other idea?
For example we could apply that to RuleDate classes to give a try.
Stef
On Oct 2, 2004, at 4:54 AM, stéphane ducasse wrote:
deprecating methods is simple and works well. Now I'm wondering how we could deprecate classes? Let them in the image in a special categoriy and redefining basicNew to use the same deprecation mechanism? Any other idea?
Good question. I was wondering how to do this with TwoWayScrollPane which is deprecated.
There are a lot of options. Moving the class to a new category called Deprecated might be good. (This would make it easy to know which classes need to be deleted in the following release.) On top of that, I guess you could redefine basicNew or new or something to use the deprecation mechanism, so that it shows up during runtime when you have deprecation warnings turned on.
Other things you could do might be adding to the class comment or adding a new method category called 'this class is deprecated'. But these are probably redundant if you've already moved the class to the Deprecated class category. So I'd say maybe just do the two things in the previous paragraph.
- Doug
For example we could apply that to RuleDate classes to give a try.
Stef
I did all of that - deprecated cat - class comment - basicNew
for ruleDate and friends in unstable following brent suggestion
Stef
On 3 oct. 04, at 20:45, Doug Way wrote:
On Oct 2, 2004, at 4:54 AM, stéphane ducasse wrote:
deprecating methods is simple and works well. Now I'm wondering how we could deprecate classes? Let them in the image in a special categoriy and redefining basicNew to use the same deprecation mechanism? Any other idea?
Good question. I was wondering how to do this with TwoWayScrollPane which is deprecated.
There are a lot of options. Moving the class to a new category called Deprecated might be good. (This would make it easy to know which classes need to be deleted in the following release.) On top of that, I guess you could redefine basicNew or new or something to use the deprecation mechanism, so that it shows up during runtime when you have deprecation warnings turned on.
Other things you could do might be adding to the class comment or adding a new method category called 'this class is deprecated'. But these are probably redundant if you've already moved the class to the Deprecated class category. So I'd say maybe just do the two things in the previous paragraph.
- Doug
For example we could apply that to RuleDate classes to give a try.
Stef
squeak-dev@lists.squeakfoundation.org