If you remember, back in the day, Galleon used to ask every so often how the people using the project wanted certain things to behave.
"QB45 will toss an overflow error if a number is outside the bounds of a variable type... Do we want to replicate this, or change it to just overflow and keep going?" <-- I remember this was one of those deliberate conversations and the user base chose to ignore QB45-compatibility and go with the overflow solution.
The LOCATE issue was just another one of those same things that he took public opinion on. "Do we just want to automatically error this out, or change to _FONT 8 instead and swap to the extra rows?"
From what I recall, almost nobody had an opinion on the subject except for Clippy -- "WTF ERROR WHEN IT DOESN'T NEED TOO?!!!?!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! THAT"S STUPID!!!!!!!!!!!!!!!!!!!!!!" And, since most people thought Clippy was just mildly rabid and didn't care enough to argue about it, that was the choice Galleon ended up going with.
And that's the history behind the "WHY" in this instance.
"QB45 will toss an overflow error if a number is outside the bounds of a variable type... Do we want to replicate this, or change it to just overflow and keep going?" <-- I remember this was one of those deliberate conversations and the user base chose to ignore QB45-compatibility and go with the overflow solution.
The LOCATE issue was just another one of those same things that he took public opinion on. "Do we just want to automatically error this out, or change to _FONT 8 instead and swap to the extra rows?"
From what I recall, almost nobody had an opinion on the subject except for Clippy -- "WTF ERROR WHEN IT DOESN'T NEED TOO?!!!?!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! THAT"S STUPID!!!!!!!!!!!!!!!!!!!!!!" And, since most people thought Clippy was just mildly rabid and didn't care enough to argue about it, that was the choice Galleon ended up going with.
And that's the history behind the "WHY" in this instance.