[Bug 1857195] Re: here string behaviour different in mksh and ksh93

2019-12-24 Thread jvdh
> Nowhere did I deliberately do anything wrt. field splitting or not- splitting or joining. understood. > I’m somewhat afraid even that, if this is wrong, it’s systematically wrong somewhere… could very well be. I even believe that ksh93 might also not do what it should/intends to do at this

[Bug 1857195] Re: here string behaviour different in mksh and ksh93

2019-12-24 Thread Thorsten Glaser
“it should be deterministic/always the same” this is a very good point, and at this, well, point, I’ve not yet got any opinion. I modelled the here strings after here documents: first, the first two “<<” are parsed indicating it’s a here document, then the here document delimiter is parsed; if

Re: [Bug 1857195] Re: here string behaviour different in mksh and ksh93

2019-12-24 Thread jvdh
On 22.12.19 21:05, Thorsten Glaser wrote: > Args, hit Return too early. > > - contact me in IRC or so if you’re up for SMTP debugging > - > https://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_05_02 > for the POSuX reference thanks (for both pointers!). -- You

Re: [Bug 1857195] Re: here string behaviour different in mksh and ksh93

2019-12-24 Thread jvdh
On 22.12.19 21:04, Thorsten Glaser wrote: > Almost a good point, considering… > > $ x=(a 'b c') > $ IFS=, > $ a="${x[*]}"; print -r -- "<$a>" > > $ a="${x[@]}"; print -r -- "<$a>" > > $ a=${x[*]}; print -r -- "<$a>" > > $ a=${x[@]}; print -r -- "<$a>" > > $ a="${u:-"${x[*]}"}"; print -r --