On 11/28/2010 2:31 PM, Nicholas Clark wrote: > On Sun, Nov 28, 2010 at 02:26:51PM -0800, Reverend Chip wrote: >> On 11/28/2010 2:34 AM, demerphq wrote: >>> However if it means we have to validate the string every time we do a >>> utf8 operation then I would say you are wrong. >> Slippery slope fallacy. > Why so? Because "validate" implies a level of caution that I have never requested, and never will. At most I've requested "don't actually crash" with a side order of "show me where I need to add protective calls to utf8::validate", which would be satisfied by, for example, avoiding invalid C pointers caused by bad utf8 and turning any invalid-utf8-caused asserts to croaks. As you well know, avoiding crashes is a much easier job than validation. Compare the gap in difficulty between code that parses valid XML correctly, and code that ensures its input is 100% valid XML.Thread Previous | Thread Next