summaryrefslogtreecommitdiff
path: root/girepository
diff options
context:
space:
mode:
authorFlorian Müllner <fmuellner@gnome.org>2013-11-29 01:12:40 +0100
committerFlorian Müllner <fmuellner@gnome.org>2013-11-29 18:45:31 +0000
commite4efb97c8a20f5dcbf6cd2736bd5bcd92e1d814d (patch)
treebaa632338c6712a1582fe0711d4c46e4f2a13637 /girepository
parent9112ec1e845015a17bba49fb1dd385a2c6e9efd7 (diff)
downloadgobject-introspection-e4efb97c8a20f5dcbf6cd2736bd5bcd92e1d814d.tar.gz
scanner: Support boolean constants
Aliasing TRUE or FALSE is not very common, but done occasionally for extra clarity. Namely G_SOURCE_REMOVE / G_SOURCE_CONTINUE are self-explanatory, unlike the "raw" booleans. https://bugzilla.gnome.org/show_bug.cgi?id=719566
Diffstat (limited to 'girepository')
-rw-r--r--girepository/girnode.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/girepository/girnode.c b/girepository/girnode.c
index 43614742..093a3783 100644
--- a/girepository/girnode.c
+++ b/girepository/girnode.c
@@ -1010,10 +1010,10 @@ parse_float_value (const gchar *str)
static gboolean
parse_boolean_value (const gchar *str)
{
- if (strcmp (str, "TRUE") == 0)
+ if (g_ascii_strcasecmp (str, "TRUE") == 0)
return TRUE;
- if (strcmp (str, "FALSE") == 0)
+ if (g_ascii_strcasecmp (str, "FALSE") == 0)
return FALSE;
return parse_int_value (str) ? TRUE : FALSE;