9 Apr
2012
9 Apr
'12
12:35 p.m.
On 9 April 2012 12:25, Stéphane Ducasse <stephane.ducasse(a)inria.fr> wrote:
On Apr 9, 2012, at 12:16 PM, Tudor Girba wrote:
Of course not, everything always continues to work.
Hi Stef,
Indeed, the change is due to Magritte 3 now using instance side annotations.
instance side annotations!!! After people cry that we change in Pharo but we do not do
such radical changes. So should we migrate the methods on the instance
side?
Check my next mail.
I do not see why Magritte is cannot be backward compatible. shit. May be we should not
use Magritte 3.
Fun isn't it. Generally a major version number means it breaks
backward compatibility.
Again have a look at the announcement: Nick even prepared automatic
refactoring to move descriptions from Magritte 1 & 2 to 3. I wished
Pharo only had a plan how to move things from one version to the other
... :-/
Now there is no magritteDynamicObject anymore ;(
It is not necessary any longer. You can on-the-fly create the objects
because the descriptions is not cached anymore.
Lukas
--
Lukas Renggli
www.lukas-renggli.ch