2 ms·
I have to admit that there is some truth there, and I apologize for implying that you were deliberately misrepresenting the issues under discussion. I wasn't gi
by mannykannot 11y ago
I have to admit that there is some truth there, and I apologize for implying that you were deliberately misrepresenting the issues under discussion. I wasn't giving much thought to your arguments because they seemed to be fundamentally missing the point, and you were probably thinking the same thing.
As it happens, I was considering the general case, and the examples of URLs and SQL came from Mike Ash's article, where he was considering the interpretation of text as information. My interpretation of cballard's post is that he regards an URL to be primarily a string, and therefore that an NSURL is, in some way, a typed string. I didn't think it was a good example, but as I was making a general point, I did not see that as mattering - I could make my point with Mike Ash's general examples instead.
My interpretation of Mike Ash's original statement is that it would be useful to have different string types where strings have different interpretations, and I disagree - the semantics of a type do not depend on its textual representation (if that were so, it would not be possible to translate those semantics between languages.) If I now understand your position correctly, it is that it is useful to have different string types because there are several different ways to interpret the underlying bit sequence as a valid string. I am not convinced that is the best solution to the problem created by us having incompatible bytes-as-text representations, but I agree that it is not wrong to consider it as an exception to the general rule.