-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
case-insensitivity for [if]
#12
Comments
If ciforth provides the standard word |
It cannot be argued that the supplied solution is non-standard, because [THEN] is not supposed to be a Forth word. It violates the principle of least surprises, though. All uses of [IF] are a mine field, anyway and I will not recommend it. I'll put this matter in the FAQ. |
Yes, if you say that the system supports the case-insensitive mode, the user expects that the words |
Op 29-08-2024 15:34 CEST schreef ruv ***@***.***>:
Yes, if you say that the system supports the case-insensitive mode, the user expects that the words [if], [else], [then] can be used in lower case too. Why not implement this?
I don't want to promote conditional compilation by [IF] where WANTED is more superior, anyway.
I don't subscribe to the notion that everything must be added that is convenient to some. Where Forth has never been designed in the first place, this is a recipee for disaster.
If lina is in case-insensitive mode, words can be found in the dictionary. [THEN] is not a dictionary word. Full stop.
You must get used to it that [THEN] will be recognized in comment and strings.
See the comment from Bernc Paysan. gforth went into the rabbit hole of ignoring [THEN] in comments,
but retraced it.
Groetjes Albert
… —
Reply to this email directly, view it on GitHub (#12 (comment)), or unsubscribe (https://github.com/notifications/unsubscribe-auth/AF6Y53JHBBYOXOBEXN22ALLZT4PNZAVCNFSM6AAAAABM65S6LCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMJXGY3TKNRXGU).
You are receiving this because you commented.Message ID: ***@***.***>
|
That's fine, no problem.
There is a
This is irrelevant to the initial problem. Anyway, yes, you cannot wrap a string literal in |
ciforth version 5.5.1
It seems,
[if]
[else]
[then]
are still case-sensitive even though"CASE-INSENSITIVE" WANTED
.The command:
Prints nothing instead of
0
.Actual output:
Expected output:
The text was updated successfully, but these errors were encountered: