summaryrefslogtreecommitdiff
path: root/giscanner/sourcescanner.h
diff options
context:
space:
mode:
authorColin Walters <walters@verbum.org>2012-10-26 16:46:05 -0400
committerColin Walters <walters@verbum.org>2012-10-30 08:20:36 -0400
commit383b0bdcc8e295d06035768062389797d3ba9262 (patch)
treee024519716913823e22abcd46294a3dc48bd9acd /giscanner/sourcescanner.h
parentce4a25dc640bdb02ff30fc233abb1c468721cbbd (diff)
downloadgobject-introspection-383b0bdcc8e295d06035768062389797d3ba9262.tar.gz
scanner: Correctly handle large 64 bit integer constants
In C, positive integer constants are by default unsigned. This means an expression like 0x8000000000000000 will be "unsigned long long". In the actual scanner code, we were parsing them as "gint64", and storing them as gint64. This was incorrect; we need to parse them as guint64, and store the bits we get from that. This gives us an equivalent result to what the C compiler does. However, when we actually return the value as a Python "long" (arbitrary length integer), we need to treat the value as unsigned if the result indicated it was. https://bugzilla.gnome.org/show_bug.cgi?id=685022
Diffstat (limited to 'giscanner/sourcescanner.h')
-rw-r--r--giscanner/sourcescanner.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/giscanner/sourcescanner.h b/giscanner/sourcescanner.h
index df16cf6a..a2834caf 100644
--- a/giscanner/sourcescanner.h
+++ b/giscanner/sourcescanner.h
@@ -126,6 +126,7 @@ struct _GISourceSymbol
gboolean const_int_set;
gboolean private;
gint64 const_int; /* 64-bit we can handle signed and unsigned 32-bit values */
+ gboolean const_int_is_unsigned;
char *const_string;
gboolean const_double_set;
double const_double;