[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: japi and public references to non-public types
From: |
Mark Wielaard |
Subject: |
Re: japi and public references to non-public types |
Date: |
Wed, 05 Oct 2005 18:47:34 +0200 |
On Wed, 2005-10-05 at 09:57 -0400, Stuart Ballard wrote:
> On 10/5/05, Jeroen Frijters <address@hidden> wrote:
> > Possibly. Maybe we can use annotations (in the -- hopefully near --
> > future) to mark code that differs from Sun for a valid reason?
>
> Perhaps I have too little faith in my fellow developers, but this idea
> scares me ;)
An annotation like that might be useful like a deprecation annotation is
useful. Then the compiler can warn that you are possibly using an
implementation specific or not-forward/backward non-abi-compatible thing
from a library. Library implementers do make mistakes. If they do there
might not be a way back, but it would be good to warn the user/developer
about it.
Cheers,
Mark
signature.asc
Description: This is a digitally signed message part
- RE: japi and public references to non-public types, (continued)
- RE: japi and public references to non-public types, Jeroen Frijters, 2005/10/05
- Message not available
- Re: japi and public references to non-public types, Stuart Ballard, 2005/10/05
- Re: japi and public references to non-public types, Tom Tromey, 2005/10/05
- Re: japi and public references to non-public types, Tom Tromey, 2005/10/07
- Re: japi and public references to non-public types, Stuart Ballard, 2005/10/07
- Re: japi and public references to non-public types, Tom Tromey, 2005/10/07
- Re: japi and public references to non-public types, Mark Wielaard, 2005/10/07
- Re: japi and public references to non-public types, Tom Tromey, 2005/10/07
RE: japi and public references to non-public types, Jeroen Frijters, 2005/10/05
RE: japi and public references to non-public types, Jeroen Frijters, 2005/10/05