« Bugzilla Issues Index
#1256 — 11.1.1.1: Handling of currency option unclear in InitializeNumberFormat
- bug_id:
1256
- creation_ts:
2013-02-19 15:58:00 -0800
- short_desc:
11.1.1.1: Handling of currency option unclear in InitializeNumberFormat
- delta_ts:
2015-02-08 14:04:49 -0800
- product:
Internationalization - ECMA-402
- component:
Specification
- version:
Edition 1.0 standard
- rep_platform:
All
- op_sys:
All
- bug_status:
RESOLVED
- resolution:
FIXED
- priority:
Normal
- bug_severity:
normal
- everconfirmed:
true
- reporter:
Norbert
- assigned_to:
Norbert
- commentid:
3199
- comment_count:
0
- who:
Norbert
- bug_when:
2013-02-19 15:58:41 -0800
The call to GetOption in step 17 returns either a String value or undefined. Step 18 uses the condition "if c is not undefined and the result of calling the IsWellFormedCurrencyCode abstract operation ... with argument c is false". It's not clear whether the "and" should be read Pascal-style or C-style. If it's read Pascal-style, then IsWellFormedCurrencyCode can be called with undefined; if it's read C-style, then it can only be called with a String value. In the latter case, the call to ToString in IsWellFormedCurrencyCode is unnecessary.
- commentid:
12221
- comment_count:
1
- who:
Norbert
- bug_when:
2015-02-08 14:04:49 -0800
Fixed in 2013-02-28 draft.