2 ms·
He forgot about stricter identifier rules, almost no product got right. Normalization. And the complete lack of unicode support in the most basic libraries or
by rurban 6y ago
He forgot about stricter identifier rules, almost no product got right. Normalization.
And the complete lack of unicode support in the most basic libraries or programs, like the libc, stdlibc++ or coreutils.
As long as you cannot compare strings, you cannot search for them.
As long as identifiers are treated as binary (e.g filesystem paths, names, ...), there are tons of security holes in the most basic things, like kernel drivers. Adding unicode support to any product does not make much sense then. Rather restrict it to Latin-1 or the current locale to be on the safe side. Nobody knows the security recommendation for identifiers.