On Sun, Jan 09, 2005 at 03:34:35PM -0500, MenTaLguY wrote:
- we're dealing with an internal string, which should always be UTF-8,
in which case c+N to advance N chars is hopelessly broken
Qualification: for skipping past the leading N whitespace characters (g_ascii_isspace), c+N is fine, as g_ascii_isspace is true only for characters that are 1 byte in UTF-8.
(I don't know whether or not this qualification is relevant to what was originally being discussed, as I don't know what was originally being discussed.)
One note of caution about Glib::ustring: The documentation claims that the internal representation is utf8, which suggests that s[i] runs in time proportional to i. However, I don't have the source handy to check this, and I have my doubts. Anyone?
If in doubt, use the iterators for passing over ustring contents rather than unsigned/int i and s[i].
pjrm.