As discussed heavily on IRC, other shells can use ((…)) or let to work
like mksh, and the mksh behaviour is semantically correct. I’ve
documented this in more detail in the manual page and the mksh FAQ now
but kept the behaviour as to not break older scripts written in mksh.
You might wish to open bugs with the other shells to make behaviour
match mksh, or warn when the underlying variable is an integer.
** Changed in: mksh
Importance: Undecided => Wishlist
** Changed in: mksh
Status: New => Fix Committed
--
You received this bug notification because you are a member of mksh
Mailing List, which is subscribed to mksh.
Matching subscriptions: mkshlist-to-mksh-bugmail
https://bugs.launchpad.net/bugs/1857702
Title:
" +=" operator does string concatenation for integer variables
Status in mksh:
Fix Committed
Bug description:
consider
typeset -i x=0; x+=1; echo $x # → 1 (as in ksh/bash/zsh)
but
typeset -i x=1; x+=1; echo $x # → 11 (rather than 2 as in the other
shells)
I believe mksh should honour the integer declaration and interpret
`+=' accordingly. currently, it does not even consistently use string
concatentation (since the first example does not yield `01' ...).
To manage notifications about this bug go to:
https://bugs.launchpad.net/mksh/+bug/1857702/+subscriptions
