3 ms·
No. If that's how it worked, how many programs would have Arabic support at all? Everyone would use EnglishString for everything (because that was the example c
by zyx321 7y ago
No. If that's how it worked, how many programs would have Arabic support at all? Everyone would use EnglishString for everything (because that was the example code they copied from StackOverflow) and the whole thing comes crashing down if I enter even just an umlaut.
- seiferteric 7y agoNo, I was thinking of something a little more sophisticated than that. Classes of strings would be sub-classed from others like English would have multiple sub-classes like American, British etc. Each class could have it's own parameters like whether it supports being reversed. You would not necessarily implement just for English. If you were making a palindrome finding app for example, you would only care if the class passed in supports reversing for example. Eventually you could have a language DB library, not so different that the time zone database that can be periodically updated with new rules.