Re: fd leak with {fd}>

On Monday, November 26, 2012 11:57:33 AM Chet Ramey wrote: > On 11/26/12 8:41 AM, Pierre Gaston wrote: > > On Mon, Nov 26, 2012 at 3:37 PM, Chet Ramey > > wrote: > > > > On 11/23/12 2:04 AM, Pierre Gaston wrote: > > > It seems rather counter intuitive that the fd is no

Re: [PATCH] Use size_t for variable list size and length

On 11/29/12 5:07 AM, Roman Rakus wrote: > see > https://www.securecoding.cert.org/confluence/display/seccode/INT32-C.+Ensure+that+operations+on+signed+integers+do+not+result+in+overflow I've actually read this. I'm skeptical that this change has any practical effect at all. I'd like to see a ca

Re: requested dry-run mode for bash.

On 11/29/12 6:30 PM, Robert Durkacz wrote: > This is a request for a new feature. Perhaps there are good reasons > why it can't be done, but from the outside looking in it seems > possible, and I have taken into account advice from the bash help > mailing list. It may be possible, but I do not thi

Re: Strange re-initialization of array. Bug or feature?

On 11/27/12 7:37 PM, Tim Friske wrote: > If sourced at least twice from another script I get the following output > printed: > > AAA > BBB > declare -A ONCE='()' > CCC > declare -A ONCE='([std.bash]="1" )' > BBB > declare -Ai ONCE='()' > CCC > declare -Ai ONCE='([std.bash]="1" )' > > If I remove

Re: How to initialize a read-only, global, associative array in Bash?

On 11/26/12 4:45 PM, Tim Friske wrote: > Hi folks, > > I execute the following code in Bash version "GNU bash, Version > 4.2.39(1)-release (x86_64-redhat-linux-gnu)": > > function foobar { > declare -rgA FOOBAR=([foo]=bar) > } > foobar > declare -p FOOBAR > # Output: declare -Ar FOOBAR='()' >