Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://github.com/nativelibs4java/BridJ/wiki/Design below:

Design · nativelibs4java/BridJ Wiki · GitHub

[JNA] made it trivial to access to native libraries from Java. Together with [https://github.com/nativelibs4java/JNAerator JNAerator], it effectively lowered the entry cost of native developments, when compared to https://en.wikipedia.org/wiki/Java_Native_Interface JNI.

However, JNA was designed in the pre-Java 1.5 era and has made some design choices that hinder both performance and usability.

BridJ was written from scratch to replace JNA with both performance and usability as golden objectives (as well as support for C++).

Performance :

• Lightweight structs : no data duplication nor synchronization issues
• Pervasive "direct" mode (heavy use of "native" Java methods)
• Assembler-optimized calls in some simple cases on select plaforms (see details below)

Usability :

• Pointer class behaves pretty much like C pointers (automatic translation is trivial)
• Enums are typed while letting users combine them as flags
• Create a C++ object with new MyCPPObject(), subclass it with new MyCPPObject() { public void myOverriddenMethod() {} }...
• Structs have chainable setters : new MyStruct().a(10).b(12)

These optimization are turned on when all conditions are met, which might be rarely or never (please read Reification for how to generate optimizable and OO-looking methods out of plain old C functions).

Without these optimizations, BridJ's performance is about the same as JNA in direct mode (without structs, where BridJ is much faster). With the optimizations, BridJ is about 10% slower than pure JNI, that is 5x faster than JNA in direct mode.

Concerns only the native C functions with primitive arguments that match the platform's size.

Supports calls with a maximum number of arguments that depends on the platform (typically, 4).

Supported platforms :

• MacOS X 64 bits
• Linux 64 bits
• Windows 32 bits
• Windows 64 bits (currently disabled)

Example of optimizable functions :

public static native int f(long a, short b, int c);

// long primitive tagged as a pointer : optimized on 64 bits platforms only
public static native int fWithPointer(@Ptr long p); 

Examples of non-optimizable function :

// p is not a primitive :
public static native int fWithPointer(Pointer<?> p);

// most supported platforms support optimization of up to 4 arguments :
public static native int fTooManyArgs(long a, short b, int c, int d, int e, int f, int g, int h, int i);

Set the environment variable BRIDJ_DIRECT=0 or set the Java property bridj.direct=false.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4