Le 1 sept. 2015 à 08:35, Marcus Denker a écrit :
On 01 Sep 2015, at 08:30, stepharo <stepharo@free.fr> wrote:
I do not get why you want to link the rewrite engine with deprecation at runtime. We should not have such dependencies. To me it is insane.
It can be made pluggable, of course. I donât want to have that there in a way that it requires the refactoring engine to be present all the time.
If itâs there â> transform. If not â> do what it does now.
But just think how much this simplifies the experience of people loading old code into a new Pharo version: it just keeps running and fixes itself! Itâs that kind of things we need to be able to evolve the system.
Imagine, this is a functionality (I think) no other system has!
I will not like a feature where it transforms my code without asking. I would prefer that a diff browser pops up and asks me if changes are ok. Automatic rewrite of code often forgot to check some specific cases and you end with bugs in your code if there is no review. The idea is great but the choice of changing the code or not has to be in the user hands.