The definition of the shift operators means that only the 5 least significant bits are used for 32-bit numbers and only the first 6 bits for 64-bit; meaning: 1 << 5 is identical to 1 << 37 (both are 32) By making it: MsgrVersion9 = 1L << 32 you make it a 64-bit number, which … Read more
WPF does support this through a type converter. It can be done by using a comma in between enum values: <ns:SomeControl Flags=”FlagA,FlagB” />
HasFlag is effectively this: HasFlag = (GivenFlag & Value) == GivenFlag; //”Anything” AND 0 == 0 –> always true
Benefits of using Flags enum: Standard approach: “They are the correct design to use when multiple enumeration values can be specified at the same time.” Intent is clear Maintainable — new programmers should pick this up easily Easily extensible — support for new flag combinations (e.g. weekend) Fast Negatives of using Flags enum: Data representation … Read more
In general I avoid using enums when designing my view models because they don’t play with ASP.NET MVC’s helpers and out of the box model binder. They are perfectly fine in your domain models but for view models you could use other types. So I leave my mapping layer which is responsible to convert back … Read more
Easiest is probably: enum Foo { blah = 1, …. all = ~0 } For unsigned based enum: enum Foo : uint { blah = 1, …. all = ~0u; }
Rationales may differ, but an advantage I see is that hexadecimal reminds you: “Okay, we’re not dealing with numbers in the arbitrary human-invented world of base ten anymore. We’re dealing with bits – the machine’s world – and we’re gonna play by its rules.” Hexadecimal is rarely used unless you’re dealing with relatively low-level topics … Read more
static IEnumerable<Enum> GetFlags(Enum input) { foreach (Enum value in Enum.GetValues(input.GetType())) if (input.HasFlag(value)) yield return value; }
The requested URL was not found on this server.
Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.