Closed
Bug 952985
Opened 12 years ago
Closed 10 years ago
\u{nnnnnn} Unicode code point escapes
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
DUPLICATE
of bug 320500
People
(Reporter: evilpies, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: feature, Whiteboard: [js:p3])
Attachments
(1 file)
6.59 KB,
patch
|
Details | Diff | Splinter Review |
I am going to do this.
Reporter | ||
Comment 1•12 years ago
|
||
Support these for strings is relatively easy. For identifier however it looks like we might need to extend the IsIdentifierStart and IsIdentifierPart function to support the whole unicode range. I am not sure if there are valid code points for that outside the 0xffff range, but I would assume so. Or maybe I misunderstood something.
Comment 2•12 years ago
|
||
It wouldn't be terribly hard to adapt our vm/make_unicode.py script to also parse DerivedCoreProperties.txt and store a flag for ID_Start - which is what we need here.
Updated•12 years ago
|
Keywords: dev-doc-needed
Reporter | ||
Comment 3•12 years ago
|
||
I think this would force us to handle the whole Unicode range, instead of just 0 - 0xffff like it's implemented right now. So this really isn't just about parsing some file, and storing a flag. Unless we add a special table just for ID_Start.
Updated•12 years ago
|
Comment 5•10 years ago
|
||
Support for \u{nnnnnn} escapes in general was added in bug 320500. Making them work in identifiers per comment 1 seems to be covered by bug 917436.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
Updated•10 years ago
|
Keywords: dev-doc-needed
You need to log in
before you can comment on or make changes to this bug.
Description
•