On Sat, Mar 28, 2009 at 2:09 PM, Sven Neumann wrote:
>> I've attached a patch for easy reference.
>
> I suggest you open an enhancement request for this at bugzilla.gnome.org
> and attach your patch there.
Sure thing:
http://bugzilla.gnome.org/show_bug.cgi?id=577231
Thanks,
-Andrew
_
Hi,
On Fri, 2009-03-27 at 15:45 -0400, Andrew Paprocki wrote:
> On Fri, Mar 27, 2009 at 1:47 PM, Andrew Paprocki wrote:
> > I checked gvalue.h and I don't see a #define in there containing the
> > proper initializer list for a GValue to prevent gcc warnings. Rather
> > than duplicating "GValue v
On Fri, Mar 27, 2009 at 1:47 PM, Andrew Paprocki wrote:
> I checked gvalue.h and I don't see a #define in there containing the
> proper initializer list for a GValue to prevent gcc warnings. Rather
> than duplicating "GValue v = {0, {{0}}};" everywhere, I'd like the
> following to be added:
>
> #d
When a GValue is declared on the stack, the large code base I work
with usually does not properly initialize the struct. (e.g. "GValue v
= {0,};") This causes gcc to print warnings when 'gcc -Wall -Wextra'
is used due to -Wmissing-braces and -Wmissing-field-initializers.
I checked gvalue.h and I d
