Re: Unexpected word splitting on $* when IFS is unset

2017-06-22 Thread Greg Wooledge
On Wed, Jun 21, 2017 at 10:30:22PM -0400, Chet Ramey wrote: > However, not all shells were consistent in their interpretation of the > Posix rules. For instance, dash, which bills itself as being completely > Posix conformant, produces 1 for that case (and expands to "ab"). The > Bourne shell (SVR

Re: AddressSanitizer: heap-use-after-free in readtok | PS1='$((b[x++}]))'

2017-06-22 Thread Chet Ramey
On 6/20/17 10:58 AM, Eduardo A. Bustamante López wrote: > I don't know how to fix this. I fixed it, it's in today's devel branch push. -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey, UTech, CWRUc...@case.edu

Re: Unexpected word splitting on $* when IFS is unset

2017-06-22 Thread DJ Mills
On Thu, Jun 22, 2017 at 7:51 AM, Greg Wooledge wrote: > On Wed, Jun 21, 2017 at 10:30:22PM -0400, Chet Ramey wrote: > > OK, going forward, I am officially considering any use of unquoted $* > or $@ in a script to be a BUG, an invocation of undefined behavior, > not acceptable, no excuses. > > I t