On 12/12/12 1:04 PM, Dan Douglas wrote:
> Hello. Could we possibly modify or create an additional variant of "typeset
> -n"
> which produces "real" references rather than just dynamic references by name?
> In other words, I'd like to be able to create reference variables that always
> point to the
On 12/12/2012 10:25 PM, Chet Ramey wrote:
That is, mind a bash-newbie question as to what this "bash+" is?
And specifically, is this nameref implementation that you speak of
something that's in the pipeline for "regular bash"?
It's the development branch of bash in the savannah git tree:
http
On 12/12/12 2:47 PM, Rene Herman wrote:
> That is, mind a bash-newbie question as to what this "bash+" is? And
> specifically, is this nameref implementation that you speak of something
> that's in the pipeline for "regular bash"?
It's the development branch of bash in the savannah git tree:
ht
On 12/12/2012 07:04 PM, Dan Douglas wrote:
While the current nameref implementation is tremendously valuable in
writing functions that manipulate non-local arrays, it does very
little else that couldn't already be done with Bash's indirect
parameter expansion, or to solve the encapsulation probl
Hello. Could we possibly modify or create an additional variant of "typeset -n"
which produces "real" references rather than just dynamic references by name?
In other words, I'd like to be able to create reference variables that always
point to the instance of a variable that was visible at the tim