rfc:unicode_escape
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
rfc:unicode_escape [2014/11/25 02:36] – Reference provision HHVM implementation pollita | rfc:unicode_escape [2017/09/22 13:28] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== PHP RFC: Unicode Codepoint Escape Syntax ====== | ====== PHP RFC: Unicode Codepoint Escape Syntax ====== | ||
- | * Version: 0.1.1 | + | * Version: 0.1.3 |
- | * Date: 2014-01-24 | + | * Date: 2014-11-24, Last Updated 2014-12-08 |
* Author: Andrea Faulds, ajf@ajf.me | * Author: Andrea Faulds, ajf@ajf.me | ||
- | * Status: | + | * Status: |
* First Published at: http:// | * First Published at: http:// | ||
Line 61: | Line 61: | ||
For all these reasons, the '' | For all these reasons, the '' | ||
- | As it happens, | + | === Prior Art === |
+ | |||
+ | ECMAScript 6 will have an identical '' | ||
+ | |||
+ | Ruby supports | ||
+ | |||
+ | (See References below) | ||
==== Encoding Rationale ==== | ==== Encoding Rationale ==== | ||
Line 72: | Line 78: | ||
This change would take place in a major version, so some level of backwards-compatibility breakage would be justified. In cases where it caused problems with existing code, fixing it could be done quite trivially by either switching to single-quoted strings, or escaping the backslash. | This change would take place in a major version, so some level of backwards-compatibility breakage would be justified. In cases where it caused problems with existing code, fixing it could be done quite trivially by either switching to single-quoted strings, or escaping the backslash. | ||
+ | |||
+ | In order to reduce backwards-compatibility issues, particularly with JSON in string literals, '' | ||
===== Proposed PHP Version(s) ===== | ===== Proposed PHP Version(s) ===== | ||
Line 85: | Line 93: | ||
Alain Williams suggested on the mailing list that we could add a named literal syntax (i.e. something like '' | Alain Williams suggested on the mailing list that we could add a named literal syntax (i.e. something like '' | ||
- | ===== Proposed Voting Choices | + | ===== Vote ===== |
As this is a language change, a 2/3 majority would be required. | As this is a language change, a 2/3 majority would be required. | ||
+ | |||
+ | Voting started on 2014-12-08 and ended on 2014-12-18. | ||
+ | |||
+ | <doodle title=" | ||
+ | * Yes | ||
+ | * No | ||
+ | </ | ||
===== Patches and Tests ===== | ===== Patches and Tests ===== | ||
Line 95: | Line 110: | ||
A language specification pull request with a patch and tests can be found here: https:// | A language specification pull request with a patch and tests can be found here: https:// | ||
- | Provisional HHVM implementation | + | Provisional HHVM implementation: |
===== Implementation ===== | ===== Implementation ===== | ||
- | After the project is implemented, | + | |
- | - the version(s) it was merged to | + | |
- | | + | |
- | - a link to the PHP manual entry for the feature | + | |
+ | No manual entry yet. | ||
===== References ===== | ===== References ===== | ||
- | * ECMAScript 6 will have the same '' | + | * Ruby supports |
+ | * ECMAScript 6 will also have this syntax: https:// | ||
===== Rejected Features ===== | ===== Rejected Features ===== | ||
Keep this updated with features that were discussed on the mail lists. | Keep this updated with features that were discussed on the mail lists. | ||
+ | |||
+ | ===== Errata ===== | ||
+ | |||
+ | The name of this RFC [[https:// | ||
===== Changelog ===== | ===== Changelog ===== | ||
- | * v0.1.1 - Added Future Scope note on named literals | + | * (2016-03-13) Added Errata |
- | * v0.1 - Initial version | + | * v0.1.3 - '' |
+ | * v0.1.2 - Ruby support | ||
+ | | ||
+ | * v0.1 - Initial version |
rfc/unicode_escape.1416882960.txt.gz · Last modified: 2017/09/22 13:28 (external edit)