Define JNIEXPORT as visibility default with GCC? (original) (raw)
Martin Buchholz martinrb at google.com
Wed Apr 10 12:50:35 PDT 2013
- Previous message: Define JNIEXPORT as visibility default with GCC?
- Next message: Define JNIEXPORT as visibility default with GCC?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Wed, Apr 10, 2013 at 1:45 AM, Anthony Petrov <anthony.petrov at oracle.com>wrote:
I totally agree that the current usage of JNIEXPORT in typedefs in AWT and 2D code is a bug.
My concern, however, is about other code that mistakenly adapted the same pattern. After this fix its compilation will fail.
Yup. Any code that was using JNIEXPORT inappropriately will fail to compile. All changes are incompatible changes.
But ... it's only a source incompatibility, only in native code, and trivial for users to fix. (It would be even better if the semantics of JNIEXPORT were documented somewhere...)
Just like the JDK native code needs porting whenever a new release of gcc comes out.
- Previous message: Define JNIEXPORT as visibility default with GCC?
- Next message: Define JNIEXPORT as visibility default with GCC?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]