3 ms·
Since this affects a huge number of applications and even desktop applications, it's a low-level library that is causing the problem. I'm not sure it's unreaso
by wvenable 9y ago
Since this affects a huge number of applications and even desktop applications, it's a low-level library that is causing the problem. I'm not sure it's unreasonable to test every unicode codepoint against shared library if that library is responsible for the rendering of unicode text.
But I agree it would be unreasonable to do that for every app that uses the library.
- jmull 9y agoYou have a point. It's probably not unreasonable to test every Unicode codepoint against a low-level shared library, at least for APIs that process a single codepoint. I don't think it's a no-brainer though. And it is unreasonable to expect a testing technique to be applied in every case where it is reasonable to do so. There are a lot of techniques that are reasonable to use in any give case but it would be no sense at all to apply every one of them. To focus on this one, now, amounts to Monday morning quarterbacking. Once you know the bug it's easy to see how it could have been caught. Of course if you somehow knew of a bug ahead of time you wouldn't need any test at all!
- wvenable 9y agoYeah, I don't disagree. Arguing this would caught by better testing is close to implying that all software bugs are avoidable; we simply have to test "better" until there are no bugs ever.