In 15.5.4.25 "String.prototype.codePointAt (pos)",
step 8 says:
Let /first/ be the code unit value of the element at index /position/
in the String /S/..
The phrase "at index" is not used anywhere else in the spec.
Instead, "at position" is used. (In fact, that was the phrase used here
in the previous draft, so it's unclear why it was changed.)
(Also, delete one of the final periods.)
made language in step 10 consistent with step 8
Also tweaked 8.4 to strengthen its use of "index". In general, I'm I want to use "index" to talk about the position of 1string elements to reenforce that we are talking about code units and not full unicode characters.
Should review the rest of the string algorithms to see if there are other places "index" should be used.
(In reply to comment #1)
>
> Should review the rest of the string algorithms to see if there are other
> places "index" should be used.
In rev24, "at position" is used (for strings) in:
7.2.9 / step 5.{c,d,e}
9.4.3.1 / step 12
18.2.6.1.1 / step 4.b, 4.d.iii.3
18.2.6.1.2 / step 4.b, 4.d.{iii,iv}, 4.d.vii.7.{b,c,d}
21.1.3.1 / step 8
21.1.3.2 / note, step 8
21.1.3.3 / note
21.1.3.6 / step 12
21.1.3.8 / step 11
21.1.3.9 / step 12
21.1.3.16 / step 10
21.1.3.17.1 / step 4
B.2.1.1 / step 6.a
B.2.1.2 / step 6.a, 6.b.i
B.2.3.1 / step 11
fixed in rev30 editor's draft
fixed in rev30