g_string_new_len(const gchar *, GSSIZE) (glib-2.0)

[Mark Mielke <mark mark mielke cc>]

If the GString structure uses gsize, why does g_string_new_len() use
gssize?

Usually this won't present a problem, but I am curious as to why I
should need to code around this limitation for the case that it
might actually be a problem.

The same argument applies to g_string_insert_len(), g_string_append_len(),
and g_string_prepend_len().

Specifically, I am dealing with code that might use a GString to hold
a very large piece of data, with little range structures to refer to
pieces of the string. If necessary, I may need to copy the piece of
the string into its own string in order to perform local
modifications. g_string_new_len() appears to be the perfect candidate
for this... except that it uses gssize as an argument.

Cheers,
mark

-- 
mark mielke cc/markm ncf ca/markm nortelnetworks com __________________________
.  .  _  ._  . .   .__    .  . ._. .__ .   . . .__  | Neighbourhood Coder
|\/| |_| |_| |/    |_     |\/|  |  |_  |   |/  |_   | 
|  | | | | \ | \   |__ .  |  | .|. |__ |__ | \ |__  | Ottawa, Ontario, Canada

  One ring to rule them all, one ring to find them, one ring to bring them all
                       and in the darkness bind them...

                           http://mark.mielke.cc/