Proposal: Put @Native and @GenerateNativeHeader in same package (original) (raw)
Alan Bateman Alan.Bateman at oracle.com
Tue Mar 5 15:28:37 UTC 2013
- Previous message: Proposal: Put @Native and @GenerateNativeHeader in same package
- Next message: Proposal: Put @Native and @GenerateNativeHeader in same package
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 05/03/2013 15:15, Paul Benedict wrote:
:
Both are hints for tools. Both discuss header files. So why divide them up? I think they should be in one package together. Personally, I think both are better suited to the javax.tools.annotation package. I just wanted to point out the division doesn't make all that sense. The reason that @Native was moved from javax.tools to j.l.annotation is because it was problematic for future modularization - ie: it would result in a compilation time dependency on the tools module and would also prevent its use in the base/core module.
-Alan.
- Previous message: Proposal: Put @Native and @GenerateNativeHeader in same package
- Next message: Proposal: Put @Native and @GenerateNativeHeader in same package
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]