Re: abstract naming conventions

From: Silvio Bierman (sbierman_at_idfix.nl)
Date: 04/13/04 

Date: Tue, 13 Apr 2004 15:23:14 +0200

"Shemp" <stoogemaniac@mchsi.com> wrote in message
news:btRec.30344$rg5.48802@attbi_s52...
> 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!
>
>

Usually the name of a class would indicate some of it's characteristics. It
being abstract is just one, don't see why that should neccesarily be encoded
in its name. The second option seems in contradiction with the convention
that classnames start with an uppercase letter.

Silvio Bierman

Relevant Pages

  • abstract naming conventions
    ... We are having a debate in our organization about naming conventions for ... abstract classes. ... The three proposed methods are: ... Prefix the class name with abstract. ...
    (comp.lang.java)
  • Re: abstract naming conventions
    ... > We are having a debate in our organization about naming conventions for ... The three proposed methods are: ... > 1) Prefix the class name with abstract. ... Look at the problems that the debate is ...
    (comp.lang.java)
  • Re: UI Question: Protecting Critical Delete?
    ... I don't prefix variables either. ... such naming conventions are no ... meta data that is easily available. ... Rick Brandt, Microsoft Access MVP ...
    (comp.databases.ms-access)
  • Re: Object oriented best practices // Creating Objects and ObjectColletions from DataLayer
    ... Another question I had was naming conventions in SQL 2000. ... Currently I prefix my columns like ... I seen Microsoft do UserID as UserID ... use Pascal casing in most cases and camel casing in parameters. ...
    (microsoft.public.dotnet.framework)