Le 04/09/2013 11:52, Igor Stasenko a écrit :
I don't understand where the tragedy is.. you want your production code to work in Pharo 2.0? Write it to work well in 2.0, don't care about 3.0 or any other future possible changes. Want your code to work on bleeding-edge 3.0 image? Refactor/do the changes to make it work.. leave 2.0 behind.
It's very tempting to do that, effectively. Want SmaCC on 3.0? Sorry, I'm only using 2.0, so you're on your own :( Want smart suggestions in Nautilus in 2.0? Sorry, not implemented.
You want both? So, keep 2 separate versions for each version of system.
And appreciate how the attitude makes it more complex than it has to be.
You just have to accept that there is no code which will magically stay compatible with all old and all possible future versions without any changes.
Yes, and its hard enough for people to appreciate any effort made in helping smooth out the transition.
Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95
