Re:The dangers of streaming across versions of glibc: A caut...
by barrkel on Tuesday January 08, 2019 @11:48AM
(#18856966)
That's one way to implement case-insensitive lookup. OTOH, for a programming language symbol table, maybe you want to look up with case sensitivity first, then a second time with case insensitivity so you can emit a warning about the discrepancy (for a case-insensitive language) or an error with suggested spelling correction (for a case-sensitive language) and you don't want to maintain two separate hash tables for every scope.
[ Parent
| on HN ]
There are no comments on this comment yet.