Re: coproc state wrongly inherited by subshell

2017-12-06 Thread Tobias Hoffmann
On 03/12/17 21:14, Chet Ramey wrote: On 11/29/17 5:36 PM, Tobias Hoffmann wrote: Description: As stated in the man page, bash will only allow a single coproc at a time. Thus, when a first coproc has already ended, a second one can be created. This can e.g. be verified by commenting out the uppe

Re: Missing documentation of the integer range (declare -i)

2017-12-06 Thread Chet Ramey
On 12/6/17 7:35 AM, H.-Dirk Schmitt wrote: > Checked against: GNU bash, Version 4.4.12(1)-release (x86_64-pc-linux- > gnu) > > I carefully read the man page and find no definition of the defined > range of integer variables in bash. > see also: `man bash |& grep -i integer` It's machine-depend

Re: Missing documentation of the integer range (declare -i)

2017-12-06 Thread Chet Ramey
On 12/6/17 7:53 AM, Greg Wooledge wrote: > On Wed, Dec 06, 2017 at 03:35:51PM +0100, H.-Dirk Schmitt wrote: >> I carefully read the man page and find no definition of the defined >> range of integer variables in bash. > > Bash uses signed 64-bit integers for arithmetic, since version 2.05b. > Befo

Re: Missing documentation of the integer range (declare -i)

2017-12-06 Thread Greg Wooledge
On Wed, Dec 06, 2017 at 03:35:51PM +0100, H.-Dirk Schmitt wrote: > I carefully read the man page and find no definition of the defined > range of integer variables in bash. Bash uses signed 64-bit integers for arithmetic, since version 2.05b. Before that, it was either 32-bit or platform-defined;

Missing documentation of the integer range (declare -i)

2017-12-06 Thread H.-Dirk Schmitt
Checked against: GNU bash, Version 4.4.12(1)-release (x86_64-pc-linux- gnu) I carefully read the man page and find no definition of the defined range of integer variables in bash. see also: `man bash |& grep -i integer` Best Regards, H.-Dirk Schmitt