You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The largest precision floating point type we support is 64bit, native and Java double.
But there exists an additional precision type built into the language, long double which is supposed to be at least as precise as double. See more on Wikipedia
We should support this native type by allowing users to map native long double to Java's BigDecimal which is the standard way of storing floating point numbers that cannot fit into double. This may need an annotation from users to help JNR-FFI know exactly what is being desired. An example mapping would look like this:
This may be much more difficult than it initially seems for multiple different reasons:
There is no standard size for long double, the only requirement is it is at least as precise as double, on x86it is 80-bits except using Microsoft Visual C++ where it is the same as double (of course 🤦), on aarch64 and powerpc it is 128 bits on GNU/Linux, See the Wikipedia page for more
We may need JNI support, meaning we may need to add new functionality into jnr-jffi, this is a problem because it means we would need to recompile the JNI for each of the platforms we support and they are very many! I don't think this will be the case, but if it is, then we can't proceed with this, since it is way too many platforms (including many obscure and rare ones) to build for.
We would also need to implement (or at least add) this for Structs, Unions and Pointers, since they can contain this native type.
This might be more work than it's worth, but I think it's worth at least investigating and logging the findings for when one day this may be more worthwhile pursuing.
The text was updated successfully, but these errors were encountered:
The largest precision floating point type we support is 64bit, native and Java
double
.But there exists an additional precision type built into the language,
long double
which is supposed to be at least as precise asdouble
. See more on WikipediaWe should support this native type by allowing users to map native
long double
to Java'sBigDecimal
which is the standard way of storing floating point numbers that cannot fit intodouble
. This may need an annotation from users to help JNR-FFI know exactly what is being desired. An example mapping would look like this:C function:
Java:
This may be much more difficult than it initially seems for multiple different reasons:
long double
, the only requirement is it is at least as precise asdouble
, onx86
it is 80-bits except using Microsoft Visual C++ where it is the same asdouble
(of course 🤦), onaarch64
andpowerpc
it is 128 bits on GNU/Linux, See the Wikipedia page for moreStruct
s,Union
s andPointer
s, since they can contain this native type.This might be more work than it's worth, but I think it's worth at least investigating and logging the findings for when one day this may be more worthwhile pursuing.
The text was updated successfully, but these errors were encountered: