Update:
In addition to $read and /filter benefiting from case-sensitive searches, so could other text scanning functions like $fline and $hfind, which currently allow this only with regex patterns which many users are not familiar with and which comes with its own bag of special symbols.
--
For $hfind a 'c' switch could modify the 'nWw' to be case-sensitive matches.
--
For $fline which has a bitmask parameter for the switches, this could be additional bitmasks.
T parameter now:
1 = listbox
2 = regex
New:
4 = non-regex search is literal text
8 = non-regex search is case-sensitive
16 = non-regex search is substring match
Bitmask 4 would allow searching for 'hello?' without also finding 'hello ' and 'hello!' and 'hello.' and 'phellogen'
Bitmask 8 would allow searching for case-sensitive spelling of a word or wildcard without also finding case-insensitive matches
In effect, the missing functionality of operators like
if ($1 == hello?)
if ($1 === hello?)
if (%string iswmcs $1)
if (%string isincs $1)
If $fline used T=2 regex bitmask, either the T=4 bitmask should be ignored or a syntax error. T=8 could either be ignored or could disable the /i flag. Is probably simpler to have T=2 make it ignore T=4/8.
