Oh, that’s an interesting use case. It’s not easy no make predictions further
in stack so by default it is assumed that the change should happen in the
method that has called the deprecated one. In fact usually this should help
with the method deprecation, and in the particular case we are deali
Ah okay!
But how does the system resolve it ? I mean, the class RTLabelled does not
refer to RTLabeled. So, what is the magic behind your tool?
I found an interesting situation. Look at this:
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
Hi Alex,
this is not about critics…
If you have a method like
labeledObject
^ RTLabelled new
in the latest roassal image and you will execute it, you will get a debugger
deprecation warning with an option to fix that.
Cheers.
Uko
> On 21 Mar 2016, at 14:07, Alexandre Bergel wrote:
