On Aug 30, 2011, at 1:23 AM, Sean P. DeNigris wrote: > I want to add a comment to #deprecated:on:in: > > This is my understanding (it is implemented inconsistently in 1.4 update > #14112): > > For methods: > 1. Have the method call deprecated:on:in: as its first step > - the versionString should be e.g. 'Pharo1.4' (although I found #Pharo1.4, > see the problem; and '1.4', those were mine, hee hee). Is it redundant to > say 'PharoXxx'? > 2. Move the method to protocol e.g. deprecated14 for Pharo 1.4 > this protocol could be an extension of the deprecatedXX package but not necessarily. because sometimes we want to keep the method longer
> For classes: > 1. Move to Category e.g. 'Deprecated14' for Pharo 1.4 > 2? Should #deprecated:on:in: be called from the methods? It's inconsistent > in the image and seems unnecessary, except maybe for some class-side > methods. Yes because this is a lot of work and not convincing :) > > Is all this correct? > > Thanks. > Sean > > -- > View this message in context: > http://forum.world.st/Deprecation-policy-tp3777647p3777647.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >
