Re: abstract naming conventions
From: ErstwhileIII (erstwhileiii_at_netscape.net)
Date: 04/29/04
- Previous message: ilaria: "JAVAMIX P2P - need Java programmers"
- In reply to: Shemp: "abstract naming conventions"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Thu, 29 Apr 2004 13:44:38 -0400
Shemp wrote:
> We are having a debate in our organization about naming conventions for
> abstract classes. The three proposed methods are:
>
> 1) Prefix the class name with abstract. Example: AbstractUser
> 2) Prefix the class name with a: Example aUser
> 3) Don't do anything to the class name.
>
> I would appreciate hearing what everyone else is doing for naming abstract
> classes.
>
> Thanks!
>
>
Option 3 is the best choice. Do not be tempted to go down the path of
overloading the class name with attributes of the class (which could,
perhaps, change over time). Look at the problems that the debate is
trying to resolve. There may be some other issue hidden here
(documentation and training on the classes being used for new
developers? fuzzy or imprecise or improper class decomposition for the
system being created? other?).
Regards,
ErstwhileIII
- Previous message: ilaria: "JAVAMIX P2P - need Java programmers"
- In reply to: Shemp: "abstract naming conventions"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
