Closed FoundOne closed 1 year ago
According to 3.4.2, case insensitivity is implementation-defined, and only the upper case version has to work.
I sometimes hesitate whether to make name lookups case insensitive, but it's not code that brings be much joy (and could break compatibility with case-sensitive systems).
One use-case where this might be important is when loading third party packages. Because other forth implementations support lowercase as well, package authors tend to go with that variant sometimes.
For example, https://theforth.net/package/sprintf/current-view/sprintf.fth
Isn't FORTH a case insensitive programming language? How to reproduce:
1 2 3 .s
What it should do: It should print the stack, i.e.1 2 3 ok
What it does: Throws an error:undefined word: .s