March 25, 2017
6:46 p.m.
It is not a new project. It started with Pharo3. Then I see no reason why I can't load the Voyage code of the time of Pharo4, with the matching code version. It should be still there, is not the purpose of Configuration? Or may be I misunderstand how version is working and its purpose. Hilaire Le 25/03/2017 à 18:08, Esteban Lorenzano a écrit :
then aside that⦠one thing I do not understand is why you are develop a new project with an old (and not maintained anymore) Pharo version? Currently supported version is Pharo5, and even if Voyage is an external project, usually development follows Pharo stable versionâ¦
-- Dr. Geo http://drgeo.eu