From: Lars Gullik Bjønnes (larsbj_at_[hidden])
Date: 2002-05-25 06:48:32
"John Maddock" <john_maddock_at_[hidden]> writes:
>> The reason for that rule is to allow things like:
>>
>> enum flags { none = 0, first = 0x01, second = 0x02, third = 0x04 };
>> flags fst = flags(first | second | third);
>
| Good point I over-reacted there, however the point is that the
| implementation is almost bound to generate the rather worrying compiler
| warnings that Neil reported. I can't see any easy way to suppress them
| either.
The easy way is to add a "default:", but that is not really nice.
(or to add the identifier that it complains about, but this would be
really bad...)
-- Lgb