,---------------. | Contributions | `---------------´ ,------------------------------------------ | 2026-10-26 20:48:56 finnw wrote: | requestClarification - Using a separate stack for `>R`, `R>`, `R@` and friends | see: https://forth-standard.org/standard/core/toR#contribution-450 `------------------------------------------ Does a system actually need to place these values on the return stack? Could it use a separate, dedicated stack for this? Or to put it another way, is there any way for a standard program to detect that this is happening? ,---------. | Replies | `---------´ ,------------------------------------------ | 2026-10-01 21:41:03 ruv replies: | proposal - Case insensitivity | see: https://forth-standard.org/proposals/case-insensitivity#reply-1760 `------------------------------------------ > ASCII characters are matched case-insensitively. All other characters are matched exactly (case sensitively). For reference, it is known as "ASCII case-insensitive comparison" [in HTML 5](https://www.w3.org/TR/2014/REC-html5-20141028/infrastructure.html#case-sensitivity-and-string-comparison) and [in Infra](https://infra.spec.whatwg.org/#ascii-case-insensitive) (extracted from HTML Living), and "HTML ASCII Case-Insensitive Collation" [in XPath](https://qt4cg.org/specifications/xpath-functions-40/Overview.html#html-ascii-case-insensitive-collation). ----- Wording should be improved as Bernd [noted](https://forth-standard.org/proposals/case-insensitivity#reply-321) (concerning environmental restrictions). ----- One question: does this change allow a standard system to provide ASCII case-insensitive matching in one word list and case-sensitive matching in another word list?