As I recall, Peter Coad had a nice summary of the advantages of using the "I" prefix for interfaces in Java Design:
http://www.amazon.com/exec/obidos/ASIN/0139111816/qid=940430526/sr=1-15/002-0300451-4975441
Erik
--
Erik Huddleston, [EMAIL PROTECTED]
Chief Architect, eCustomers.com
Microsoft Java MVP
> -----Original Message-----
> From: Javier Borrajo [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, October 20, 1999 8:58 AM
> To: [EMAIL PROTECTED]
> Subject: Re: EJB naming conventions?
>
>
<snip>
>
>
> When I go through pages of code/javacode I like any help I can get.
> Knowing some type is an interface and not a class helps me a lot.
>
> + I know I cannot do a "new" on that type
> + I know the classes I develop may implement that interface,
> perhaps to use them as method parameters in libraries that
> use the interface as a formal parameter
> + I know I can use the type as a contract with external components
> + ...
>
> I know those facts just form the type name, without having do any more
> investigation. IMHO that's helpful information.
>
> Regards
>
> Javier
>
> ==============================================================
> =============
> To unsubscribe, send email to [EMAIL PROTECTED] and
> include in the body
> of the message "signoff EJB-INTEREST". For general help,
> send email to
> [EMAIL PROTECTED] and include in the body of the message "help".
>
