Re: Return codes over 1 byte

2015-07-14 Thread Eric Blake
On 07/09/2015 05:30 PM, Michael DePaulo wrote: > mark06 mentioned this on IRC today and then left the channel about 1 hour > later: > > has anyone ever discussed exit codes above one byte? they are > valid on modern windows, but cygwin's bash will mess them POSIX requires that all sizeof(int) b

Re: Return codes over 1 byte

2015-07-10 Thread Corinna Vinschen
On Jul 9 20:20, Michael DePaulo wrote: > On Thu, Jul 9, 2015 at 7:42 PM, Yaakov Selkowitz > wrote: > > On Thu, 2015-07-09 at 19:30 -0400, Michael DePaulo wrote: > >> mark06 mentioned this on IRC today and then left the channel about 1 hour > >> later: > >> > >> has anyone ever discussed exit c

Re: Return codes over 1 byte

2015-07-09 Thread Michael DePaulo
On Thu, Jul 9, 2015 at 7:42 PM, Yaakov Selkowitz wrote: > On Thu, 2015-07-09 at 19:30 -0400, Michael DePaulo wrote: >> mark06 mentioned this on IRC today and then left the channel about 1 hour >> later: >> >> has anyone ever discussed exit codes above one byte? they are >> valid on modern window

Re: Return codes over 1 byte

2015-07-09 Thread Yaakov Selkowitz
On Thu, 2015-07-09 at 19:30 -0400, Michael DePaulo wrote: > mark06 mentioned this on IRC today and then left the channel about 1 hour > later: > > has anyone ever discussed exit codes above one byte? they are > valid on modern windows, but cygwin's bash will mess them > > I was curious, so I go

Return codes over 1 byte

2015-07-09 Thread Michael DePaulo
mark06 mentioned this on IRC today and then left the channel about 1 hour later: has anyone ever discussed exit codes above one byte? they are valid on modern windows, but cygwin's bash will mess them I was curious, so I googled it (I could not find an answer) and then tried it out. I can confir