On 4/16/22 09:04, sminervini.prism wrote: > It is still the case that I and others need Java floating point and StrictMath > (the key double type calculator class) to be repaired.
If you are going to pursue this line of reasoning, you must be aware of some things. Firstly, it is not possible to change Java's core floating-point arithmetic in a compatible way. We certainly will not adopt decimal floating-point for Java's core arithmetic. Secondly, Java should not be your focus. We will not change Java's arithmetic in a way that is incompatible with other languages or which makes Java slower on existing hardware. You must read and fully understand this before you go any further. It will require a lot of study: https://docs.oracle.com/cd/E19957-01/806-3568/ncg_goldberg.html > May the Java Community Process reconsider the present floating point > operations and method calls situation, based on an imperfect > standard and improper workaround, and provide corrected, defaulting > or specifying-compatible waya for Java floating point arithmetic and > Calculator class method results to always cohere in their ranges, > without denormal and pronormal inclusion? In a word, no. That possibility is so unlikely that it is not worthy of consideration. -- Andrew Haley (he/him) Java Platform Lead Engineer Red Hat UK Ltd. <https://www.redhat.com> https://keybase.io/andrewhaley EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671
