Such errors could slip code review by and cause random inexplicable runtime errors for quite some time. And string operations could accidentally break up the unicode characters. Using them would cause the length of the string to not be what the user thinks it is. Same with dashes, underscores, and many other characters. For example, there's a number of characters that render like spaces but are actually multibyte unicode characters. One case where Mimic could sneak past the compiler (and code review) but still cause problems would be inside strings. But some of the aforementioned ideas (or variants thereof) would be just brilliantly evil, to the point that the code works fine when you leave, but say three months later it starts rarely breaking at random times and locations, and the "code plague" just gets more and more common with time.
Unless your code review system is lax, or (best) if you have write access to the repository.
There's a number of examples here, although some would be harder to sneak past code review than others. Time-delayed or rarely-occurring "evil" can often be better.
0 kommentar(er)
