@Wayne,
I am guessing the probability to encountering this bug is low: the parser stops reading a token if a space is found. So encountering a UTF8 sequence that contains the 0x20 byte (and is not the "space" char) is perhaps not frequent.
@Wayne,
I am guessing the probability to encountering this bug is low: the parser stops reading a token if a space is found.
So encountering a UTF8 sequence that contains the 0x20 byte (and is not the "space" char) is perhaps not frequent.