docs: Amend the docs for g_str_equal() to reflect current general usageac690d9a8c3297967415f97dabaeff9adb796668109/head
| commit | ac690d9a8c3297967415f97dabaeff9adb796668 | |
| author | Philip Withnall <withnall@endlessm.com> | |
| Thu, 14 Jun 2018 17:12:42 +0000 (14 18:12 +0100) | ||
| committer | Philip Withnall <withnall@endlessm.com> | |
| Thu, 14 Jun 2018 17:12:42 +0000 (14 18:12 +0100) | ||
| tree | 44a9659f2acdd6feab10a44bc062e2670b207ceb | treesnapshot (tar.gz zip) |
| parent | 2fe4fa6cd06191304a76bbc2ddf1bc341b84f424 | commitdiff |
docs: Amend the docs for g_str_equal() to reflect current general usage
People do (and should) use g_str_equal() for string comparisons outside
of hash tables, because it’s easier to read than
`strcmp (str1, str2) == 0`. That should not be discouraged.
However, we should still be careful to point out that g_str_equal() is
not NULL-safe, and g_strcmp0() is.
Signed-off-by: Philip Withnall <withnall@endlessm.com>
People do (and should) use g_str_equal() for string comparisons outside
of hash tables, because it’s easier to read than
`strcmp (str1, str2) == 0`. That should not be discouraged.
However, we should still be careful to point out that g_str_equal() is
not NULL-safe, and g_strcmp0() is.
Signed-off-by: Philip Withnall <withnall@endlessm.com>
| glib/ghash.c | diffblobblamehistory |