Hi, If you have scripts you call with the command line argument 'eval' like this:
./pharo eval '1+2. Smalltalk snapshot: true andQuit: true' you will get into problems in Pharo 2.0 (e.g., a debugger with 'stdout is closed' message). Pharo 3.0 does not have this problem. The correct way to do that in Pharo 2.0 is: ./pharo eval --save '1+2' which is non-arguably much cleaner :-) -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill
