|
|
|
Re: [PATCH] add warnings enum-to-int and int-to-enum | |
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] | |
On Tue, 1 Sep 2009, Stephen Hemminger wrote:
> there is lots of code that does:
>
> enum {
> my_register_1 = 0x001,
> my_register_2 = 0x002,
> };
It feels to me like the explicit numeric values are what make these
constants sensible to use directly as ints, and that it's only sensible to
use a non-constant value of an enum type as an int (without an explicit
cast) if all of the enum values have explicit numeric values.
I think:
enum {
my_register_zero
...
my_register_twdr
my_register_twcr
...
};
void () {
write_register(my_register_twdr, SETUP_TWDR);
}
is asking for trouble in a way that this warning is about.
-Daniel
*This .sig left intentionally blank*
--
To unsubscribe from this list: send the line "unsubscribe linux-sparse" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
[Newbies FAQ] [Kernel List] [Site Home] [IETF Annouce] [DCCP] [Netdev] [Networking] [Security] [Bugtraq] [Photo] [Yosemite] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Linux SCSI] [DDR & Rambus] [Trinity Fuzzer Tool]