Re: [Pharo-dev] Stdio>>#standardIOStreamNamed:forWrite: bug?

2018-08-06 Thread Alistair Grant
On Mon, 6 Aug 2018 at 12:18, Damien Pollet wrote: > > Yes, they do, at least on my macOS. > > I have some doubt about #stdioIsAvailable though… before there was a possible > value of 4 (cygwin terminal) for the file descriptor type, which is now out > of the tested range, is that intentional

Re: [Pharo-dev] Stdio>>#standardIOStreamNamed:forWrite: bug?

2018-08-06 Thread Damien Pollet
Yes, they do, at least on my macOS. I have some doubt about #stdioIsAvailable though… before there was a possible value of 4 (cygwin terminal) for the file descriptor type, which is now out of the tested range, is that intentional On Mon, 6 Aug 2018 at 12:00, Guillermo Polito wrote: > Damien,

Re: [Pharo-dev] Stdio>>#standardIOStreamNamed:forWrite: bug?

2018-08-06 Thread Guillermo Polito
Damien, Could you check that at least the proposed image-side changes fix your problem for *nixes? On Sat, Aug 4, 2018 at 7:13 PM Sean P. DeNigris wrote: > Alistair Grant wrote > >> Tracking issue: > >> https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/274 > > The issue above is for the

Re: [Pharo-dev] Stdio>>#standardIOStreamNamed:forWrite: bug?

2018-08-04 Thread Sean P. DeNigris
Alistair Grant wrote >> Tracking issue: >> https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/274 > The issue above is for the VM changes. > > The issue for image changes is: > https://pharo.fogbugz.com/f/cases/22296/Stdio-file-creation-fixes Thanks for looking into this, Alistair! Few are

Re: [Pharo-dev] Stdio>>#standardIOStreamNamed:forWrite: bug?

2018-08-04 Thread Alistair Grant
On Sat, 4 Aug 2018 at 15:43, Alistair Grant wrote: > > > > > I don't think the error handling has been changed in a long time, but > > just looking quickly at the source code, I think you're correct that it > > isn't returning the correct values. It should be returning nil for > > those handles

Re: [Pharo-dev] Stdio>>#standardIOStreamNamed:forWrite: bug?

2018-08-04 Thread Alistair Grant
On Fri, 3 Aug 2018 at 11:24, Alistair Grant wrote: > > Hi Guille, > > On Fri, Aug 03, 2018 at 10:34:22AM +0200, Guillermo Polito wrote: > > Hi, > > > > I don't know the windows situation at all, but I'm wondering. > > > > ([ File stdioDescriptorIsATTY not ] > > on: PrimitiveFailed > > do: [ :ex |

Re: [Pharo-dev] Stdio>>#standardIOStreamNamed:forWrite: bug?

2018-08-03 Thread Alistair Grant
Hi Guille, On Fri, Aug 03, 2018 at 10:34:22AM +0200, Guillermo Polito wrote: > Hi, > > I don't know the windows situation at all, but I'm wondering. > > ([ File stdioDescriptorIsATTY not ] > on: PrimitiveFailed > do: [ :ex | "HACK kept for retrocompatibility" Smalltalk os isWin32 ]) > ifTrue: [

Re: [Pharo-dev] Stdio>>#standardIOStreamNamed:forWrite: bug?

2018-08-03 Thread Guillermo Polito
Hi, I don't know the windows situation at all, but I'm wondering. ([ File stdioDescriptorIsATTY not ] on: PrimitiveFailed do: [ :ex | "HACK kept for retrocompatibility" Smalltalk os isWin32 ]) ifTrue: [ ^ self createStdioFileFor: moniker ]. the first thing I would do, just trying to keep the

[Pharo-dev] Stdio>>#standardIOStreamNamed:forWrite: bug?

2018-08-02 Thread Alistair Grant
Hi Damien, Vincent and Guille, Just a disclaimer: despite having done some work on this, I don't consider myself an expert. If someone else has a better explanation, please jump in. Damien wrote on discord: > is there a notion of standard input/output on windows ? Yes, console applications