Well, whatever you guys choose to believe, please no one try to "fix"
it as this behaviour appears to be consistent across the board - at
least as far as JS, Minerva and SMSQ/E are concerned. If programmers
keep their indices in order the issue should never arise anyway.
Per
On 13/01/2024
I wonder if part of the reason that this arose is that some BASICs
from that era just returned a null string "" if string slicing errors
arose, without an error message and people remembered that?
While that was probably convenient for the casual programmer, it must
have made debugging difficult
Norman Dunbar wrote:
I still think that returning "" for a specific string slice from (a to
a-1) is a bug!
I tend to agree. x$ (a to b) where b is smaller than a should rise an
error.The only way that would make any kind of sense to me would be if
this returned the array contents in the
