6 ms·
Please support your argument against correctness by providing an example where an INVALID string as input to a suitable modified generic string function would r
by codehero 7y ago
Please support your argument against correctness by providing an example where an INVALID string as input to a suitable modified generic string function would result in a valid string.
- dooglius 7y agoIt's not an "argument against correctness" it's an argument to what you are proposing
- codehero 7y agoI don't understand the fallibility. Clearly misuse of string functions is epidemic. A propagating INVALID string result makes it very clear there is a logic error and not an exploit. I understand how one could shoot down implementations, but none has made a convincing argument about shooting down the idea.
- RhysU 7y agoWhat is length of an invalid string? What is the length of the concatenation of two invalid strings? There are sensible answers. But they are weird.
- codehero 7y agoIs it more sensible to cat 2 strings, but cut off the second one, then pass off the result as valid? I would say let an INVALID string be length 0. Then accept that catting a valid and invalid string would result in a shorter length. Which one do you think is safer?
- RhysU 7y agoI would expect an invalid string to have an invalid length. For integer-valued lengths you'd have to use a negative number to differentiate from a valid, empty string. But then the sum of the invalid-string lengths differs from the length of the concatenated invalid strings. Which is wonky.
- codehero 7y agoSafe string manipulation never exceeds the bounds of the buffer. So negative values are dangerous, as all as any additions that would exceed the maximum size. Negative lengths are not compatible with unsigned representation. A system implementing invalid string values must choose a text encoding such as UTF-8 that supports the concept of an invalid character. Null termination is too flexible. As such is simple length prepending.