New API Design Guideline: Enums

Coding Standard: Enums standards, fresh and crispy

Ken Brubaker — Tue, 18 May 2004 21:00:00 GMT

Brad Abrams clued us in to the revised Enum usage guidelines.

re: New API Design Guideline: Enums

Daniel Pratt — Tue, 18 May 2004 19:51:00 GMT

What would be the downside to changing the way values are automatically assigned to enum "members" (without an explicit value assignment) if the "Flags" attribute is present?

re: New API Design Guideline: Enums

Nicholas Allen — Tue, 18 May 2004 21:25:00 GMT

One thing I don't like about these guidelines is that modifying an enum is considered acceptable. Most strong enum implementations (which admittedly .net is not trying to provide) define this as a compatibility breaking change. The guideline even goes on to say

Developing with the suspected future versioning of an enum in mind is the required attitude.

Which is pretty much acknowledging that changing a widely known enum type will break a lot of code.

Link Interface 30.

UnknownReference — Wed, 19 May 2004 18:34:00 GMT

Link Interface 30.

Link Interface 30. - The Chaotic-Neutron

Link Interface 30. - The Chaotic-Neutron — Tue, 03 Feb 2009 21:31:29 GMT

PingBack from http://www.chaoticneutron.com/2004/05/19/link-interface-30/