Re: strsplit question (glib)
- From: Havoc Pennington <hp redhat com>
- To: Peter Jay Salzman <p dirac org>
- Cc: gtk-list gnome org
- Subject: Re: strsplit question (glib)
- Date: 29 Apr 2002 00:46:57 -0400
Peter Jay Salzman <p dirac org> writes:
> ok, so now search_path points to an array of strings. the docs don't
> say a "NULL terminated array of strings". just an array of strings.
> how do i know how many strings are being pointed to? in other words,
> how do i use this array when i have no idea how many elements are in
> this array?
It is NULL terminated, this is just a glib convention (all the string
util things that deal with arrays of strings deal with NULL-terminated
arrays in which each string in the array is a separate malloc'd
Probably not in the docs since the docs author considered it obvious
(without NULL termination there's no way the API could possibly work,
and it's a glib-wide convention anyhow). But might be nice to add to
> another question -- glib provides a GString. perhaps the most useful
> thing in glib. why in the world would g_strsplit work with arrays of
> char *'s instead of g_arrays of GStrings?
Because g_strsplit() is a utility function for handling C strings, not
Most apps use GString only when building up a string with lots of
appends or the like, and use plain char* for most strings. A GArray
of GString would be a really error-prone, cumbersome pain in the ass.
] [Thread Prev