#commonSqueak or something like that , which is for pharo and squeak (but not gemstone)
It's called "squeakCommon" and I have no idea if "gemstone" means the pharo based gemstone image
Not, that's GemTools. Gemstone, is the Smalltalk gemstone.
or the server. Anything I see is that FFI config also uses #common and developers for it are Esteban, you and Dale.
I didn't do the FFI ;) In addition, if you see all the confs I announced I put everything in #pharo because I didn't test it in squeak. Actually, at the beginning, I put everything in #common but then Dale suggest me to put them in #pharo if I only tested there, and that's what I did. If them someone test it in squeak or gemstone, and works ok, then we can put it as common. But yes, everything that uses FFI, I think should be only in Squeak and Pharo as Gemstone does not support a "similar" FFI.
So you should know ;)
However - what if Metacello gets ported. Do we have an "commercialSmalltalksCommon", "vastAndVW", ... or any other combination or do we have to maintain a spec for any each platform.
Would'nt it be better to have a spec and tell on which (multiple) targets it is able to run.
+1 I totally agree. That solution doesn't scale. The ideal would be if for: can also an array, as load: do for example: You can do load: 'aGroup' or load: #('group1' 'group2' ) So, maybe would be cool to do: for: #('squeak' 'pharo' .... ) what do you think? Questions over Questions ...
Bye T.
-- Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3.5 - sicherer, schneller und einfacher! http://portal.gmx.net/de/go/chbrowser
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project