Hello: FWIW, we use "Enum" as a postfix, for example JmsPropertyEnum. To me, a type, is an interface or a class, or a data-type. "Type" does not convey to me the idea that the object has a limited pre-defined set of values.
Gary > -----Original Message----- > From: Stephen Colebourne [mailto:[EMAIL PROTECTED] > Sent: Saturday, March 25, 2006 2:47 AM > To: Jakarta Commons Developers List > Subject: Re: [poll] [pool] picking descriptive class names > > Sandy McArthur wrote: > > The main behavior of the composite pools are configured via four > > type-safe enum types. I'll describe what each type controls and then > > suggest name variants. Let me know which one you think is the most > > self-evident and user friendly. Feel free to suggest new names. > > We use the suffix Type for all enums at work. It seems to work well. > > The suffix strategy implies that the class actually does real > calculations or business logic IMO. The behaviour suffix is yucky. The > policy suffix could be OK. > > Stephen > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
