Jacqueline: But…. a byte is a byte is 8 bits, unicode may be 2 bytes per char, or not, right? I don’t see where unicode would come into simple byte addressing. But then, you may be right that somehow unicode stuff has gotten into the mix somehow. Bill On Sep 10, 2014, at 10:32 AM, J. Landman Gay <jac...@hyperactivesw.com> wrote:
> On 9/10/2014, 8:28 AM, Alex Tweedly wrote: >> In 6.7 (DP1), the times to copy chars or bytes are equal and very small, >> while the number for lines is quite small. >> >> In 7.0 RC1, the times are all *MUCH* larger - to the point where I'd >> say 7.0 is unacceptable. >> And in addition, copying bytes takes over twice as long as copying chars >> - when if anything it should be the other way round. > > That's kind of why I thought it was counting, but whatever is causing it, I'm > pretty sure it has to do with parsing Unicode and multi-byte codepoints. When > you have more than one byte per character, it may not be possible to > calculate the exact text position without counting something. > > -- > Jacqueline Landman Gay | jac...@hyperactivesw.com > HyperActive Software | http://www.hyperactivesw.com > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
