Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.java.programmer > #36429
| Newsgroups | comp.lang.java.programmer |
|---|---|
| Date | 2017-04-06 02:44 -0700 |
| References | <c5d8020b-2092-45c0-b0ad-377923357d6a@googlegroups.com> <obv3gf$15k3$1@gioia.aioe.org> |
| Message-ID | <db29f576-4b8e-420a-9274-3ab4264502cd@googlegroups.com> (permalink) |
| Subject | Re: Reuse naming *Provider in other classes |
| From | lewbloch@gmail.com |
On Monday, April 3, 2017 at 8:22:00 PM UTC-7, omegajunior wrote: > I tend to prefix interface classes with I, and abstract ones with > A. I've seen JDK and JRE classes suffixed Impl if they are an > implementing sub class. Those prefixes do not conform to the Java naming conventions. The Java API itself uses `Abstract` as a prefix for abstract classes, which has the virtue of conforming to the camel-case, compound-word convention. The suggested standard for interfaces is to use simple nouns or adjectives, like `List` or `Comparable`. Sometimes slightly more compound words are indicated, like `SortedSet`, but the names are still very type-like. -- Lew
Back to comp.lang.java.programmer | Previous | Next — Previous in thread | Find similar | Unroll thread
Reuse naming *Provider in other classes mike <mikaelpetterson@hotmail.com> - 2017-03-10 04:24 -0800
Re: Reuse naming *Provider in other classes Andreas Leitgeb <avl@logic.at> - 2017-03-10 12:37 +0000
Re: Reuse naming *Provider in other classes mike <mikaelpetterson@hotmail.com> - 2017-03-10 05:29 -0800
Re:Reuse naming *Provider in other classes omegajunior <omegajunior@protonmail.com> - 2017-04-03 23:21 -0400
Re: Reuse naming *Provider in other classes lewbloch@gmail.com - 2017-04-06 02:44 -0700
csiph-web