July 2, 2012
7:02 p.m.
Yes, the hack in 2.0 is just to allow us to run the tests on windows (and avoid complete break of image in the platform, as it has happened before), and is not intended to be there on release. The real issue, however, is not so easy to solve, but I hope we can find a solution sometime soon :) Esteban On Jul 2, 2012, at 8:42 PM, Torsten Bergmann wrote:
Unfortunately the discussion/actions stopped:
http://forum.world.st/STDIO-on-Win-td4631056.html
Any chance we can get VM support STDIO support in Pharo 2.0 for Win32 also?
The current hack in #standardIOStreamNamed:forWrite: has some side effects (see issue #6236).
Thx T.