- 3,741,519 Users
- 2,248,443 Discussions
- 7,861,847 Comments
- 381.3K All Categories
- 2.1K Data
- 204 Big Data Appliance
- 1.9K Data Science
- 446.6K Databases
- 220.6K General Database Discussions
- 23 Multilingual Engine
- 511 MySQL Community Space
- 462 NoSQL Database
- 7.7K Oracle Database Express Edition (XE)
- 2.8K ORDS, SODA & JSON in the Database
- 448 SQLcl
- 3.9K SQL Developer Data Modeler
- 185.6K SQL & PL/SQL
- 20.8K SQL Developer
- 291.8K Development
- 7 Developer Projects
- 117 Programming Languages
- 288.6K Development Tools
- 94 DevOps
- 3K QA/Testing
- 645.3K Java
- 18 Java Learning Subscription
- 36.9K Database Connectivity
- 150 Java Community Process
- 104 Java 25
- 22.1K Java APIs
- 137.7K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 12 Java Essentials
- 141 Java 8 Questions
- 85.9K Java Programming
- 79 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.2K Java SE
- 13.8K Java Security
- 197 Java User Groups
- 193 LiveLabs
- 34 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 165 Deutsche Oracle Community
- 1.2K Español
- 1.9K Japanese
- 225 Portuguese
Big Issue with float, double, Java Floating Point.
I have found that double and float types in java are heirs to arithmetic underflow and overflow at any use.
I have found that presently, floating point is an arithmetic approximation. My problem is that
the java language needs to be changed here, so that one may have arithmetic accuracy with
floats and doubles.
There is also a trigonometric shortfall when it comes to BigDecimal.
I have attempted to, and have more carefully described these problems, via the java bugs database:
-These types, as things are, must be computationally discarded, used only in terms of push and pull,
and be programmed around using BigDecimal, which will be a waste of memory,
program execution speed, and a total confusion due to the lack of any operator
usage options on BigDecimals.
-It is the case that set, get methods, constructors and mutability methods are all based
around float and double, not BigDecimal, which is part of the previous problem.
-It is the case that setting up BigDecimals can be and is a circumstantial waste of memory
with very many tasks, combined with the fact that the fact that having to use BigDecimal
method calls is nowhere near as efficient or legible to developers or mathematics and enginner
programmers (and useful with their time) as
+, -, *, /, %, +=,-+,*=,/=,%=, ++, --
.This is a syntax argument largely, but also an instruction argument
since BigDecimals have to be set up or used with an extra, thereby second, call.
-It is the case that every other major language includes both floating point and accuracy mode
options with these two types and or Objects, either as a source code instruction or as a
compiler switch option. These languages at least provide both options for floating
point and mathematical accuracy mode.
-It is so that the present arithmetic underflow and underflow are total disadvantages,
that need only be altered in place, for preconditions, postconditions and in place.
This is in regard to programs that have been compiled and built already.
-My Oracle Support technical reviews seem not to recognise these real problems in
technical analysis, or only interpret matters in terms of the
Java Language Specification on these issues, which of itself possesses inadequecies in these places.
Can someone please reply to me on these things?
Can Oracle update the Java SE language?