On 10 February 2013 17:28, Stefan Marr <smalltalk@stefan-marr.de> wrote:
Hi Stef:
Begin forwarded message:
because now it only works on 2.0 So I will use symbolic versions for real. I think that you are working on 2.0. On 1.4 I get DNU due to substrings...
What's the best way to handle such trivial difference between different versions, or even dialects?
So, the problem is basically #includesSubString: vs. #includesSubstring:, used by a single method.
Creating a version specific package just for that methods seems to be exaggerated.
However, you committed now Phexample-StephaneDucasse.68 that is based on Phexample-StefanMarr.67. I think, in general that will lead to mighty confusion because it is not a general fix, but Pharo 1.4 specific. The latest version now breaks on Pharo 2.0 again (with a deprecation...)
Wouldn't it have been better to properly branch off this change and commit it to Phexample.Pharo1.4-StephaneDucasse.68 for instance?
Any other good approach to handle such small differences in a scalable way would also be interesting...
Given that Squeak suffers this particular problem as well (at least for the moment...), perhaps a compatibility shim might be in order? Non-Pharo-2.0 images simply file in a compatibility package that lets them use Phexample. It keeps the problem where it belongs: in those images that still have a horrible mEthodNaMe. frank
Thanks Stefan
-- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 2974 Fax: +32 2 629 3525