On 21 January 2016 at 12:08, Marek Olšák maraeo@gmail.com wrote:
On Thu, Jan 21, 2016 at 11:51 AM, Emil Velikov emil.l.velikov@gmail.com wrote:
On 18 January 2016 at 22:53, Marek Olšák maraeo@gmail.com wrote:
Try explaining that to people who have a compulsion to fix them or argue about them. :) Ignore? REALLY? IGNORE???
Now that we have a few people off your back can you please point out where this triggers warnings ?
This particular warning is trigged by {}
As mentioned previously neither {} nor {0} trigger any warning here. Jani hinted that you might be using an old (buggy?) compiler which generates them. Which version of GCC are you using ? Do you mind showing the first few warnings ?
or any { ... } which doesn't initialize all members.
Do we have any outside of intel_decode.c ? I'm failing to spot any.
-Emil