I call them API ex:
http://www.sandrasf.com/other/sandra/javadoc/index.html?org/sandra/api/package-summary.html
and Impl.
.V
Larry Meadors wrote:
At any rate, it boils down to personal preference. As the tech lead
where I work, I would publicly flog anyone who committed a
ICustomerDao class to my C
> But that is irrelevant, it is NOT necessary to distinguish
> from similarly named classes because of the package structure
> and/or class naming.
6.2.1 Naming Interfaces
The Java convention is to name interfaces using mixed case with the first
letter of each word capitalized. The
preferred Ja
> But that is irrelevant, it is NOT necessary to distinguish
> from similarly named classes because of the package structure
> and/or class naming.
6.2.1 Naming Interfaces
The Java convention is to name interfaces using mixed case with the first
letter of each word capitalized. The
preferred Ja
On Sat, 26 Feb 2005 15:30:12 +0100, <[EMAIL PROTECTED]> wrote:
> I just googled a bit :-)
>
> Interface. When necessary to distinguish from similarly named classes:
> InterfaceNameEndsWithIfc.
> Class. When necessary to distinguish from similarly named interfaces:
> ClassNameEndsWithImpl OR
> Clas
Hmm,
> "Abstract" describes the behavior (the class is an abstract
> or partial implementation), where "I" is just a name
> mangler...I suppose you
> *could* argue that it describes the *lack of* behavior, but
> that still seems like nonsense. ;-)
I just googled a bit :-)
Interface. When nec
Hmm,
> "Abstract" describes the behavior (the class is an abstract
> or partial implementation), where "I" is just a name
> mangler...I suppose you
> *could* argue that it describes the *lack of* behavior, but
> that still seems like nonsense. ;-)
I just googled a bit :-)
Interface. When nec
6 matches
Mail list logo
