Re: [Pharo-users] Backward compatibility [WAS] Re: [ANN] PharoDev-1.3-13173
On May 2, 2011, at 12:48 AM, Markus Fritsche wrote:
Hi,
2011/4/27 Mariano Martinez Peck <marianopeck@gmail.com>:
And as Marcus said, most of the times (sometimes we had some problems) we have a deprecation process where we (usually) say which should be used instead.
From a a-little-bit-more-than-user perspective I am looking at
SmalltalkImage>>#hasBindingThatBeginsWith: aString self deprecated: 'Use Smalltalk globals'. ^globals hasBindingThatBeginsWith: aString
Maybe we should not deprecate that quite yet but have it as a compatibility method (like at:put:)
Well, with a bit of analysis, I would be able to figure out, that the author might have intended that I should search the SystemDictionary myself. I feel like an additional comment would have been helpful.
Same with the other problem I had with ServiceRegistry - it is gone and it is not easy to find out what that was supposed to do. Next step is to compare squeak and the Pharo releases to find out what happened to it (the issue tracker does not easily yield results for this, but maybe I searched in the wrong way).
Services brought lots of complexity without being used too much. We should build menues via pragmas (like the world menu), then extensions ot menues are just extension methods. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.
participants (1)
-
Marcus Denker