2011/12/29 Benoit St-Jean <[email protected]>: > I was wondering what is planned regarding packages available on SqueakSource > and Pharo. More and more packages can't load in Pharo and it gets more and > more frustrating not being able to load anything without having to > add/modify methods/classes all over the place so those packages can load > properly in Pharo. Are we looking at a Pharo-only kind of SqueakSource in > the future ? > > Besides, having to handle platform specific (i.e. Pharo vs Squeak) for every > package is adding more complexity than what is needed. I know backward > compatibility was thrown away from the start to avoid compromises in Pharo > but how do we take care of the fact that as each day passes, less and less > stuff from SqueakSource is usable in Pharo ?
This is not a direct reply to your concerns, but maybe Pharo should stick to this convention regarding the semantic versioning in the future: http://semver.org/ This implies that a public API should be established clearly and maybe this is not for tomorrow ;-) I wondering if the conformity check to this specification could be automatically done in Pharo. I guess yes because we have access to all the code with MC. Regards, -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Matsuno Laboratory, Kyoto University, Japan (until 12/2011) http://www.mechatronics.me.kyoto-u.ac.jp/ Every DSL ends up being Smalltalk http://doesnotunderstand.org/
