« Bugzilla Issues Index
#2864 — UnicodeEscapeSequence and Contextual Keywords
- bug_id:
2864
- creation_ts:
2014-05-13 20:13:00 -0700
- short_desc:
UnicodeEscapeSequence and Contextual Keywords
- delta_ts:
2014-06-16 16:10:22 -0700
- product:
Draft for 6th Edition
- component:
technical issue
- version:
Rev 24: April 27, 2014 Draft
- rep_platform:
All
- op_sys:
All
- bug_status:
RESOLVED
- resolution:
FIXED
- priority:
Normal
- bug_severity:
minor
- everconfirmed:
true
- reporter:
Kevin Smith
- assigned_to:
Allen Wirfs-Brock
- commentid:
8407
- comment_count:
0
- who:
Kevin Smith
- bug_when:
2014-05-13 20:13:11 -0700
In 11.6.2, we have:
"Code point in a ReservedWord can not be expressed by a \ UnicodeEscapeSequence"
but there appears to be no such restriction for contextual keywords. Is this intentional?
Thanks!
- commentid:
8413
- comment_count:
1
- who:
Allen Wirfs-Brock
- bug_when:
2014-05-14 10:24:50 -0700
Contextual keys are expressed in the grammar as literal character sequences that do not include unicode escape sequences. The same is true of ReservedWord. In all places where unicode escapes are allowed (summarized in the NOTE in clause 10), they are explicitly enumerated by the grammar.
It's probably best to turn the text you quote in 11.6.2 into a NOTE so that it doesn't carry any implication that it might not apply to contextual keywords,
- commentid:
8488
- comment_count:
2
- who:
Kevin Smith
- bug_when:
2014-05-15 04:35:33 -0700
Got it. I agree that changing that text into a note would probably be helpful to the reader.
Thanks!
- commentid:
8512
- comment_count:
3
- who:
Allen Wirfs-Brock
- bug_when:
2014-05-15 15:56:32 -0700
fixed in rev25 editor's draft
- commentid:
9012
- comment_count:
4
- who:
Allen Wirfs-Brock
- bug_when:
2014-06-16 16:10:22 -0700
fixed in rev25 editor's draft