Name: skT88420 Date: 10/21/99
To reproduce the bug, do this.
java.text.DecimalFormat.applyPattern("#0.#e0");
You will get this.
Exception in thread "main" java.lang.IllegalArgumentException:
Unexpected '0' in pattern "#0.#e0"
at java.text.DecimalFormat.applyPattern(DecimalFormat.java:1552)
The problem is that bug 4068067, noted with 1.1 has never been
adequately addressed. The addition of the character 'E', as
a hardcoded character for Exponential and Scientific Notation,
is erroneous on the one hand, and totally inconsistent with
the general WORA as well as Internationalization philosophy.
If someone with a few weeks of experience were to review
proposed solutions to problems like this, then JavaSoft might
not get so embarrassed when such a thing as a hardcoded 'E'
is implemented and released.
If the general philosophy of "NO HARDCODING" were implemented,
then this shortsightedness would have been caught by JavaSoft,
and not the developer community, where we have to put up with
such inanity.
What is required is well documented, I am not going to demean
JavaSoft any further by going into details here.
(Review ID: 96860)
======================================================================
To reproduce the bug, do this.
java.text.DecimalFormat.applyPattern("#0.#e0");
You will get this.
Exception in thread "main" java.lang.IllegalArgumentException:
Unexpected '0' in pattern "#0.#e0"
at java.text.DecimalFormat.applyPattern(DecimalFormat.java:1552)
The problem is that bug 4068067, noted with 1.1 has never been
adequately addressed. The addition of the character 'E', as
a hardcoded character for Exponential and Scientific Notation,
is erroneous on the one hand, and totally inconsistent with
the general WORA as well as Internationalization philosophy.
If someone with a few weeks of experience were to review
proposed solutions to problems like this, then JavaSoft might
not get so embarrassed when such a thing as a hardcoded 'E'
is implemented and released.
If the general philosophy of "NO HARDCODING" were implemented,
then this shortsightedness would have been caught by JavaSoft,
and not the developer community, where we have to put up with
such inanity.
What is required is well documented, I am not going to demean
JavaSoft any further by going into details here.
(Review ID: 96860)
======================================================================
- relates to
-
JDK-4068067 RFE: Want API to access exponent symbol in DecimalFormatSymbols
-
- Resolved
-