Re: GLib String support

2008/8/11 Mathias Hasselmann <mathias hasselmann gmx de>:
> Remains the question: Why are their ASCII only versions of all those
> functions. Dunno. Legacy? Performance? Side note: Why don't have Intel's
> fancy processors some g_utf8_next_char() function yet?

The reason there are ASCII-only versions of string functions is for
protocols, parsing config files, etc.  For example if you were
implementing the HTTP protocol, you (probably) don't want to accept
any Unicode number when reading the status code, etc.

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]