04.06.14 17:49, Paul Sokolovsky написав(ла): > On Thu, 5 Jun 2014 00:26:10 +1000 > Chris Angelico <rosuav at gmail.com> wrote: >> On Thu, Jun 5, 2014 at 12:17 AM, Serhiy Storchaka >> <storchaka at gmail.com> wrote: >>> 04.06.14 10:03, Chris Angelico написав(ла): >>>> Right, which is why I don't like the idea. But you don't need >>>> non-ASCII characters to blink an LED or turn a servo, and there is >>>> significant resistance to the notion that appending a non-ASCII >>>> character to a long ASCII-only string requires the whole string to >>>> be copied and doubled in size (lots of heap space used). >>> But you need non-ASCII characters to display a title of MP3 track. > > Yes, but to display a title, you don't need to do codepoint access at > random - you need to either take a block of memory (length in bytes) and > do something with it (pass to a C function, transfer over some bus, > etc.), or *iterate in order* over codepoints in a string. All these > operations are as efficient (O-notation) for UTF-8 as for UTF-32. Several previous comments discuss first option, ASCII-only strings.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4