The danger of over simplification: Enum.IsDefined()

RE: The danger of over simplification: Enum.IsDefined()

Frank Hileman — Sun, 30 Nov 2003 07:30:00 GMT

I wasn't too happy to discover, by using a profiler, that Enum.IsDefined is taking a significant fraction of CPU in our app that uses System.Drawing. There are some checks in there, and there is nothing we can do to get rid of them.

RE: The danger of over simplification: Enum.IsDefined()

Ian Griffiths — Mon, 01 Dec 2003 18:58:00 GMT

Even worse, Enum.IsDefined ignores the [Flags] attribute. Given the following: [Flags] enum Foo { X = 1, Y = 2 } the value Foo.X | Foo.Y is allowed. But Enum.IsDefined indicates that it's not a valid value!

RE: The danger of over simplification: Enum.IsDefined()

sharpie — Mon, 01 Dec 2003 19:36:00 GMT

Therefore would it be safe to say one should simply not be using Enum.IsDefined for anything at all? If there is no good reason for it, why does it exist? WIll it be deprecated in a future release?

RE: The danger of over simplification: Enum.IsDefined()

vitabath — Sat, 06 Dec 2003 04:25:00 GMT

RE: The danger of over simplification: Enum.IsDefined()

James — Wed, 17 Dec 2003 02:58:00 GMT

Why not make Enum.IsDefined inlined at compiletime like a #define -- that's essentially what you're asking us to do in our verification code. If there's a standard thing that we should be doing, there should be a compiler/tool way to make it automated. I guess there's some value to making people look at it, but I think it's less of a benefit than making IsDefined (or some IsDefinedAtLastCompile equivalent) easier to do (and therefore more likely to be done). IMHO, there would probably be more errors by people's manual maintenance of this validation code than by not having to handedit the values and missing the assumptions broken by the introduction of new values.

DateTime Compatability Issue

Brad Abrams — Tue, 17 Feb 2004 19:49:00 GMT

DateTime Compatibility Issue

Brad Abrams — Tue, 17 Feb 2004 19:53:00 GMT

Enum.IsDefined

Mathew Nolton Blog — Wed, 18 Feb 2004 23:24:00 GMT

How useful are enums?

Mathew Nolton Blog — Wed, 18 Feb 2004 23:57:00 GMT

A compilation of new .NET Design Guidelines

Ken Brubaker — Fri, 20 Feb 2004 18:46:00 GMT

For my own reference, I thought I'd compile a quick list of design guidelines added by Brad Abrams, et al.

re: Enum Switches

Omer van Kloeten's .NET Zen — Mon, 19 Apr 2004 20:50:00 GMT

re: Enum Switches

Omer van Kloeten's .NET Zen — Mon, 19 Apr 2004 23:29:00 GMT

Working with Enums

Darrell Norton's Blog [MVP] — Wed, 25 May 2005 16:35:06 GMT

Geoff wrote a whole bunch of code for dealing with Enums. Enums are annoying because you can cast any...

re: C# Tips: Enumなプロパティのsetterの冒頭は

菊池 Blog — Tue, 14 Mar 2006 09:35:03 GMT

re: C# Tips: Enumなプロパティのsetterの冒頭は

C# Enum.Parse() Bug « The Pursuit of a Life

C# Enum.Parse() Bug « The Pursuit of a Life — Tue, 11 Dec 2007 10:21:41 GMT

PingBack from http://xidey.wordpress.com/2007/12/10/c-enumparse-bug/