Stable APIs (was Re: [squeak-dev] Re: Why isn't Squeak 4.1 updating?)

Frank Shearar frank.shearar at
Tue Apr 20 13:23:48 UTC 2010

Casimiro de Almeida Barreto wrote:
> Em 20-04-2010 09:27, Bert Freudenberg escreveu:
>> (...)
>> It could well be that methods that were deprecated before are finally removed in trunk. We cannot promise full backwards-compitibility forever, otherwise we would have no chance of ever getting a cleaner system.
> Ok. Nothing is compatible forever... not even C/C++ things over time.
>> What would help immensely is if we could define what APIs we consider to be stable and supported. These need to be documented, and changes would need to be documented for each new release too.
> As a tip, besides external documentation it would be convenient if
> deprecated classes and methods/messages got commented ("Deprecated:
> will/may be removed in next releases"). Also comments like
> "Experimental: behavior may change in next updates" and "Alpha"/"Beta"
> would be useful.

Do we need, in the image at least, something more than Object>>deprecated: ?


More information about the Squeak-dev mailing list