Re: [eclipse-dev] Best practices for provisional APIs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

Re: [eclipse-dev] Best practices for provisional APIs

From: Gunnar Wagenknecht <gunnar@xxxxxxxxxxxxxxx>
Date: Fri, 17 Feb 2006 16:07:22 +0100
Delivered-to: eclipse-dev@xxxxxxxxxxx
List-archive: <http://eclipse.org/pipermail/eclipse-dev>
List-help: <mailto:eclipse-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/eclipse-dev>, <mailto:eclipse-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/listinfo/eclipse-dev>, <mailto:eclipse-dev-request@eclipse.org?subject=unsubscribe>
User-agent: Thunderbird 1.5 (Windows/20051201)

Gunnar Wagenknecht schrieb:
> It should have ".internal." in the package name. It doesn't make sense
> if you found public API where the JavaDoc says: "Hey don't use me! I
> *may* chance". If it's internal then people know that it *will* chance
> and they are prepared for some refactoring work.

s/chance/change
Sorry for the typo.

Cu, Gunnar

-- 
Gunnar Wagenknecht
gunnar@xxxxxxxxxxxxxxx
http://wagenknecht.org/

References:
- [eclipse-dev] Best practices for provisional APIs
  - From: Pascal Rapicault
- Re: [eclipse-dev] Best practices for provisional APIs
  - From: Gunnar Wagenknecht

Prev by Date: Re: [eclipse-dev] Best practices for provisional APIs
Next by Date: Re: [eclipse-dev] Best practices for provisional APIs
Previous by thread: Re: [eclipse-dev] Best practices for provisional APIs
Next by thread: RE: [eclipse-dev] Best practices for provisional APIs
Index(es):
- Date
- Thread

Breadcrumbs