About deprecated methods
ducasse
ducasse at iam.unibe.ch
Fri Sep 12 06:26:59 UTC 2003
> We could wait two versions if others feel strongly about it, though.
Me too :)
In fact I would favor to remove them all and create a package with them
so that people can still load it for documentation purpose.
> Speaking of deprecated methods, someone mentioned awhile ago that they
> thought the deprecation method should be renamed from
> #deprecatedExplanation: to just #deprecated:. I think this would be a
> good idea.
if someone wants no problem with us. But this will break our pending
changes :) but someone can do it.
Now two methods for deprecation MUST be there one for ordinary methods
and one with a block as parameter for primitives because we cannot
insert in the method body before the primitive tag a deprecation
statement.
In the next batch of changes I have move around primitives and you will
see some examples of the second methods.
> The deprecatedExplanation: method name seems too verbose for such an
> important method... verbosity is okay for the names of rarely used
> methods, but for more commonly used methods shorter is often better,
> for example #do: and not #doBlock:. :-) Also in this case when seeing
> the #deprecated: method being used it's pretty obvious that the string
> being passed along is the explanation.
>
> If we wanted to rename this method, the beginning of 3.7alpha would be
> a good time, especially if all of the senders are removed.
>
> - Doug
>
>
More information about the Squeak-dev
mailing list
|