Task #140 (closed)
Add IEnum interface
| Reported by: | jamoore | Owned by: | jamoore |
|---|---|---|---|
| Priority: | minor | Milestone: | 3.0-M3 |
| Component: | Model | Version: | 3.0-M1 |
| Keywords: | interface,enumerations,iteration1 | Cc: | |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description
It would be benefitial if all enumeration types implemented an IEnum interface. There would only be one method String getValue(); but it would make working with them simpler.
This should probably wait on or be done in conjuction with #96.
Change History (4)
comment:1 Changed 18 years ago by jmoore
- Keywords iteration3 added
- Milestone changed from Unscheduled to cycle1
comment:2 Changed 18 years ago by jmoore
- Resolution set to duplicate
- Status changed from new to closed
comment:3 Changed 18 years ago by jmoore
- Keywords iteration1 added; iteration3 removed
- Milestone changed from 3.0-M2 to 3.0-M3
comment:4 Changed 18 years ago by jmoore
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
r704 and r705 provide the start of these values, but that development happened in ITypes not IEnums. Closing IEnums ticket until ITypes (#86) is mature. It may be that ITypes will be sufficient. (See also #157 which may cause IEnums to be necessary for ease of use.)