[Vm-dev] Re: [Pharo-project] Using stdout in Windows --> 'File stdout is closed'

[Martin Dias]

On Tue, Apr 10, 2012 at 8:41 PM, Eliot Miranda <eliot.miranda at gmail.com>wrote:

>
>
>
> On Tue, Apr 10, 2012 at 4:35 PM, Martin Dias <tinchodias at gmail.com> wrote:
>
>>
>>
>>
>> On Tue, Apr 10, 2012 at 1:45 PM, Eliot Miranda <eliot.miranda at gmail.com>wrote:
>>
>>>
>>> Hi Martin,
>>>
>>>     would you please try with both the Croquet.exe and the
>>> CroquetConsole.exe in
>>> http://www.mirandabanda.org/files/Cog/VM/VM.r2540/cogwin.zip?.  The
>>> CroquetConsole.exe is designed to be used from the command line; stupidly
>>> Windows has this distinction between console apps and windows apps, and
>>> this distinction affects standard i/o.  If CroquetCOnsole works then the
>>> implication is that Pharo needs also to build both VMs and the user needs
>>> to select the console VM for console use and the Windows VM for detatched
>>> use.
>>>
>>
>> Oh, thanks, using CroquetConsole.exe it works fine.
>>
>> Now, I realized that in DOS #cr does not work fine as "new line" so I
>> changed to #crlf... this was necessary also using cygwin and another bash
>> emulator.
>>
>> But...  hmmm...
>>
>> use a special vm + use a different newline character
>>
>
> If you set its lineEndCOnvention correctly you shouldn't have to use a
> different character.  The special VM is forced by WIndows (and if you
> compare the bits you'll see they differ in only a few bytes).
>

Ok, so I will take the two alternatives into account, and I will see what
results better in the practice.


PS: I also rejected #crlf because I saw that Transcript in Pharo (at least
in 1.4 and 1.3) currently doesn't support it, so made me feel to better
don't use it. But maybe makes sense to report the issue and implement it.



>
>>  => I prefer to avoid that, just using the normal cogvm and redirect to a
>> file using ">" in command-line.
>>
>> Thank you very much!
>>
>>
>>> HTH
>>> Eliot
>>>
>>> On Sun, Apr 8, 2012 at 4:31 PM, Martin Dias <tinchodias at gmail.com>wrote:
>>>
>>>> Hi
>>>>
>>>> In my windows 7, I get an error when trying to write to "FileStream
>>>> stdout" in both Pharo 1.4 and 1.3 (revisions #14423 and #13320).
>>>>
>>>> To reproduce,
>>>>
>>>> - download:
>>>>
>>>> https://ci.lille.inria.fr/pharo/job/Pharo%201.4/373/artifact/Pharo-1.4.zip
>>>>
>>>> - evaluate:
>>>> FileStream stdout nextPutAll: 'a'.
>>>>
>>>> Is this a known issue? I couldn't find it in issue tracker.
>>>>
>>>> Thanks in advance.
>>>> Martín
>>>>
>>>
>>>
>>>
>>> --
>>> best,
>>> Eliot
>>>
>>>
>>>
>>
>>
>
>
> --
> best,
> Eliot
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/vm-dev/attachments/20120410/c6630367/attachment-0001.htm