Hi, I think the more proper API to use is
CodeImporter evaluateFileNamed: '/path/to/my/file.st'. Check CodeImporter class side for more options (streams, strings...). CodeImporter is there for already 3/4 years I think. The idea is that filing in is not a file responsibility. Guille On Mon, Apr 23, 2018 at 10:35 PM, Hilaire <hila...@drgeo.eu> wrote: > That's a plan! > > I realized from my code I was already using a mix of the new and old > world. It will be nice to get rid of the antic one to reduce the confusion > when manipulating file. > > Thanks > > Le 22/04/2018 à 20:12, Sven Van Caekenberghe a écrit : > >> It is not hard at all, just start from FileSystem (i.e. FileReference, >> FileLocator, etc, ..) and open your streams from there and you are good. I >> guess the FileSystem from the Deep into Pharo book is a good start. >> >> From a user perspective, the changes are not that big. If something is >> not clear, you can always ask. >> > > -- > Dr. Geo > http://drgeo.eu > > > > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13
