Enum
From APIDesign
(Difference between revisions)
| Line 1: | Line 1: | ||
| - | [[Java]] has been enhanced with [[wikipedia::Enumerated type|enums]] in version 1.5. The [[Enum]]s greatly simplify and standardize the way one can express the [[wikipedia::Enumerated Type|enumerated types]] in [[Java]]. However since their introduction I was not sure how suitable they are for [[API Design]] ( | + | [[Java]] has been enhanced with [[wikipedia::Enumerated type|enums]] in version 1.5. The [[Enum]]s greatly simplify and standardize the way one can express the [[wikipedia::Enumerated Type|enumerated types]] in [[Java]]. However since their introduction I was not sure how suitable they are for [[API Design]] (I was not the only one, see few year's old [[Blogs:AndreiBadea:EnumsInAPIs|Andrei's post]]). Today I finished one [[Enum]] related [[API]] change for [[NetBeans]], and I felt all the pain. I guess I understand now what is wrong with [[Enum]]s in [[API]]s. |
| + | |||
| + | |||
[[TBD]]: Story about AU.CATEGORY | [[TBD]]: Story about AU.CATEGORY | ||
Revision as of 17:40, 9 January 2011
Java has been enhanced with enums in version 1.5. The Enums greatly simplify and standardize the way one can express the enumerated types in Java. However since their introduction I was not sure how suitable they are for API Design (I was not the only one, see few year's old Andrei's post). Today I finished one Enum related API change for NetBeans, and I felt all the pain. I guess I understand now what is wrong with Enums in APIs.
TBD: Story about AU.CATEGORY
Follow
