|
|
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 dealing with a class deprecation hacked as a method deprecation :)
But it’s good that now I know more use cases ;)
Uko
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:
<Screen Shot 2016-03-21 at 10.53.09 AM.png> 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
Hi!
I cannot figure out what I should expect after loading DeprecationAssistant. I have loaded it and created a method: -=-=-=-=-=-=-=-=-= foo self deprecated: 'use bar instead’ -=-=-=-=-=-=-=-=-=
Is there anything that should be displayed in the critic list?
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
HI everyone,
You can install and try it out with: Metacello new
repository: '<a href="github://Uko/DeprecationAssistant'" class="">github://Uko/DeprecationAssistant';
baseline: 'DeprecationAssistant';
load
This will add additional actions to the debugger once you will get a deprecation warning.
Have fun! Cheers. Uko
|
Locked
