Fix stupid false positive warnings about uninitialized variables
authorMarcel Holtmann <marcel@holtmann.org>
Tue, 14 Jul 2009 04:06:46 +0000 (06:06 +0200)
committerMarcel Holtmann <marcel@holtmann.org>
Tue, 14 Jul 2009 04:06:46 +0000 (06:06 +0200)
commitfeb36e2d5b0edb882e152c1fd958166e22eb0cbd
tree7a7aed1aa5757d7b0925e6303e03efffa3a6e361
parent3d1dd9d452e341e65a4a96c5ed77cc693dcdc673
Fix stupid false positive warnings about uninitialized variables

The GCC check for uninitialized variables is so useful that dealing
with the false positives is just a minor inconvenience.

The following GCC trick helps to silence them:

#define uninitialized_var(x) x = x

This way no code obfuscation is needed to compile smoothly and the
code stays readable. And the author has to actually think about it.
src/sms.c
src/smsutil.c