> Le 22 juin 2016 à 14:05, Valentin Ryckewaert <valentin.ryckewa...@gmail.com> > a écrit : > > Hello everyone, > > i'm currently working on making Pharo able to manage if it writes on his > files.I created a class which can define it, then I'm already able, for > example, to define if Pharo writes on pharo.changes or not. > > The meaning of this is to make Pharo able to execute a script but without > being modified by it, a script shouldn't let any trace of its execution on > the image or on Pharo files. > > My problem concern PharoDebug.log, I would like to know what you prefer Pharo > to do with it in the case we configured it to not write on his files > (changes, source,image....). > Should Pharo writes the logs in the terminal ? in a tmp file ? or just in > PharoDebug.log ?
If you want to use Pharo as a script interpreter, then just do like other interpreter: report results and errors on stdout / stderr. Then, you can redirect the output to also have it in a file if you want. I would not use PharoDebug.log or any other file. Christophe
