Talk:Java Native Access

C types

I find the types section quite dubious, since it seems pretty windows oriented with the special win32 names and the (C/C++) types with the length they commonly have ON WINDOWS, on Linux for example long is can be 32 bit or 64 bit. then wikipedia is not a how-to. Flow, 145.53.104.245, 20 dec 2010 19:46 (GMT+1)

The types section is grabbed from the JNA documentation, which is where the byte sizes and such are given. IsmAvatar (talk) 08:38, 2 August 2011 (UTC)

On Linux int is 32 bits, long will be 32 bits in 32 bit mode, 64 bits in 64 bit mode, corrected above. Dfries (talk) 13:12, 12 July 2019 (UTC)

svnkit

I may be too stupid to get this idea but why would SVNKit that reportedly is a 'pure Java Subversion client library' use Java Native Access? Isn't that a case of either or? 130.246.132.26 (talk) 12:29, 6 August 2009 (UTC)

There are two downloadable versions - one with, and one without. So it is pure Java, but, with JNA, it can make some native calls for faster access. More information can be found on this page. IsmAvatar (talk) 08:43, 2 August 2011 (UTC)

Moved for discussion

Moved from the article for discussion. The following appears to have been added against WP:COI and is unsourced. Perhaps some if it could be incorporated into the article if properly sourced. --Ronz (talk) 16:31, 8 August 2008 (UTC)

Partial source is a bit I wrote on the JNA project page; I can only vouch for what happened when I took over the project; I summarized prior history from the project publication announcement. --twall 00:07, 18 October 2008 (EST)

I think the History of JNA should be moved to the Main Page. It is useful in understanding this project. — Preceding unsigned comment added by Xamalek (talk • contribs) 22:15, 30 September 2015 (UTC)

History

Fragments of the JNA project date back to a small shared stubs library originally written by Sheng Liang of the Sun Microsystems JNI team and demoed at JavaOne circa 1999.

Over the next seven years, Todd Fast (also of Sun) heavily modified Sheng's library to add full Win32 support, provide a friendlier API, and expand the ability to map native libraries, functions, and types to Java equivalents. He first published the project on java.net under the name of "Java Native Access (JNA)" in the fall of 2006. The name was intended to reflect both the similarities to and differences from the Java Native Interface (JNI), which is the standard (though relatively difficult) mechanism for accessing native code from Java.

Timothy Wall became the maintainer of the project in February 2007, and has contributed by expanding the feature set, adding linux and OSX ports, and making the library usable for more advanced function types. Wayne Meissner contributed significantly to enable a wide range of ports by incorporating libffi and enabling 64-bit targets.

In the first public release, cross-platform support was limited to Solaris and Win32 and there was only partial struct support for native calls. With the purported goal of providing a concise programming model for developers, the API took advantage of JDK 5's annotations and type safety features, though these features were later removed to support using JNA with earlier versions of the Java VM. Finally, as a result of Todd's work on the project at Sun, JNA is packaged under the com.sun domain, though most of the work on the project has since shifted to parties outside of Sun.

JNA only handles C and the C subset of C++, right?

So there is no support for overloaded functions, C++ data types (std::string, std::vector, std::map etc.) and other C++ features, or am I wrong? --RokerHRO (talk) 17:36, 3 September 2012 (UTC)

External links modified

Hello fellow Wikipedians,

I have just modified one external link on Java Native Access. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

• Added archive https://web.archive.org/web/20090523145246/http://today.java.net/pub/a/today/2009/05/19/protect-your-legacy-code-jna.html to http://today.java.net/pub/a/today/2009/05/19/protect-your-legacy-code-jna.html

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template {{source check}} (last update: 5 June 2024).

• If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
• If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—InternetArchiveBot (Report bug) 23:13, 22 November 2017 (UTC)