Bug 27564 - resources for java.text.NumberFormat#computeInstance() should be included in base LocaleInformation.properties
Summary: resources for java.text.NumberFormat#computeInstance() should be included in ...
Status: NEW
Alias: None
Product: classpath
Classification: Unclassified
Component: classpath (show other bugs)
Version: 0.90
: P3 normal
Target Milestone: ---
Assignee: Not yet assigned to anyone
Depends on:
Reported: 2006-05-11 20:36 UTC by KiYun Roe
Modified: 2006-05-16 18:03 UTC (History)
1 user (show)

See Also:
Known to work:
Known to fail:
Last reconfirmed: 2006-05-16 18:03:28


Note You need to log in before you can comment on or make changes to this bug.
Description KiYun Roe 2006-05-11 20:36:12 UTC
getNumberInstance() and getIntegerInstance() in java.text.NumberFormat call computeInstance() to perform a resource search for default format strings. These resource searches generally fail and require exception handling in computeInstance(), because the default values are not in LocaleInformation.properties or any of the other locale property files. This makes calls to getNumberInstance() and getIntegerInstance() much more expensive than necessary. This expense can be avoided simply by putting the default format strings for getNumberInstance() and getIntegerInstance() in LocaleInformation.properties. Note that the cost also propagates to java.text.MessageFormat#format(), which can make an arbitrary number of calls to getNumberInstance() and getIntegerInstance().
Comment 1 Tom Tromey 2006-05-16 18:03:28 UTC
Doing this would require changing the localegen app and re-running it.