[Pharo-project] [update 2.0] #20209

Marcus Denker marcus.denker at inria.fr
Fri Jul 13 17:01:48 EDT 2012


On Jul 13, 2012, at 10:48 PM, Sven Van Caekenberghe wrote:

> 
> On 13 Jul 2012, at 15:44, Marcus Denker wrote:
> 
>> Issue 6356:	some cleanups related to methods moved away from SmalltalkImage (vm and os related)
>> 	http://code.google.com/p/pharo/issues/detail?id=6356
> 
> OK. but how can a poor library developer trying to write code that has to remain compatible with 1.3 and 1.4 deal with this ?
> 
> Have a look at
> 
> ZnUserAgentSettings class>>#platformDetails
> 	^ self platform platformName, ' ', self platform platformSubtype, ' ', self platform osVersion
> 
> Now, this is a deprecated class in Zn as well, but rewriting 
> 
>  self platform osVersion
> 
> to
> 
>  self platform os version
> 
> does not seem to give the same result in 1.4 
> 
> Any suggestions ?

maybe we need to concept of pre-deprecation?

Then we can pre-deprecate a method, and a version later deprecate it, and then remove it...

In general: staying compatible forever means no change. That is possible, too.

	Marcus


--
Marcus Denker -- http://marcusdenker.de





More information about the Pharo-dev mailing list