On Sun, May 20, 2012 at 4:59 PM, Igor Stasenko <siguctua@gmail.com> wrote:

On 20 May 2012 21:34, Eliot Miranda <eliot.miranda@gmail.com> wrote:
> Hi�Torsten,
>
> On Sun, May 20, 2012 at 11:51 AM, Torsten Bergmann <astares@gmx.de> wrote:
>>
>> Hi,
>>
>> havent yet played with the latest stdin/stdout stuff.
>> Does this already work on Windows?
>>
>> At least I tried
>>
>> FileStream stdout nextPutAll: 'Yopla'
>>
>> in the latest 2.0 after starting Pharo-2.0-one-click.bat.
>> Gives an error (write failed).
>>
>> Any comments?
>
>
> It works in my console VMs. �If you download
> e.g.�http://www.mirandabanda.org/files/Cog/VM/VM.r2550/cogwin.zip�you need
> to run CroquetConsole.exe in a DOS or Cygwin window. �Using the normal VM
> does *not* work, since that's the way Windows is "designed".
>

Nope. It just requires some work :)

Come on :) �The program opening up a completely different console isn't what I'd call working. �And if the program is in a pipe ist must stay in a pipe. �Its an easy thing to have a console VM, e.g. run from a script.

�

***
One of the common misconceptions surrounding Win32 programming is that
you must decide early in the design process whether your application
will be a console or GUI application. In reality, console applications
can create windows and have a message loop just like a GUI application
(see "Adding Graphics to Console Applications" by Michael Covington,
Visual Developer, June/July 1997). Alternatively, graphical
applications can create and use a console. Although Win32 provides
functions for communicating with a console, they are a little clumsy
to use and require parameters that are unnecessary for simple text
I/O. This article shows how to use standard C/C++ I/O with consoles,
and how to work around specific problems in the Visual C++ I/O
library.
***
http://dslweb.nwnexus.com/~ast/dload/guicon.htm

> --
> best,
> Eliot
>

--
Best regards,
Igor Stasenko.