3 ms·
> Then again I would avoid anything non-8 bit for asset parsing. Nitpick: you probably meant non-7 bit (there's a reason why ruby and python2 default to non-ex
by lloeki 14y ago
> Then again I would avoid anything non-8 bit for asset parsing.
Nitpick: you probably meant non-7 bit (there's a reason why ruby and python2 default to non-ext ascii source code, and barf at you otherwise)
- malkia 14y agoYup. 7-bit, but the point is even if character above 127 were used it would've been okay. 7-bit (8-bit) ASCII has a long life to live :) It's just machine optimal, and the same time not flexible for modern days needs... just like "C", and I love it. I'm using Qt5 these days, and there is QString and QByteArray (and also QLatin1String) - and I need to keep in memory lots of properties for our editor, going to QString (wide-chars) just uses more memory for no reason. Sticking to QByteArray/QLatin1String makes more sense for them.
- yxhuvud 14y agoThe default changed to utf8 in Ruby for 2.0 though, so I suppose that reason is less obvious than you think.