gobject: don't use G_STRLOC in G_OBJECT_WARN_INVALID_PSPEC() macro
authorThomas Haller <thaller@redhat.com>
Wed, 17 Dec 2014 09:00:35 +0000 (10:00 +0100)
committerThomas Haller <thaller@redhat.com>
Thu, 18 Dec 2014 14:02:16 +0000 (15:02 +0100)
commitc447bc7f93fbc6e1aaf7f46eef9da2f820c8f209
tree86a9255381f53652e6318ca9f4c621299e1b9d80
parentd951db4236146efd8f4f343740d50433739526c8
gobject: don't use G_STRLOC in G_OBJECT_WARN_INVALID_PSPEC() macro

Using G_STRLOC ends up embedding unique strings of the form
__FILE__:__LINE__ in the compiled binary. We can avoid these
by passing __FILE__ and __LINE__ separately when constructing
the warning text.
This probably reduces the size of the binary as __FILE__ is
likely already contained as string otherwise.

Note that for GCC 2.x this changes behavior because G_STRLOC
also contained __PRETTY_FUNCTION__.

https://bugzilla.gnome.org/show_bug.cgi?id=741654
gobject/gobject.h