-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Misc Editorial re recent commits #1023
Merged
Merged
Changes from 1 commit
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
b5794dd
Editorial: fix 2 typos from recent commit
jmdyck 296f6e0
Editorial: Add blank lines in multi-prodn <emu-grammar>s
jmdyck 8de9d52
Editorial: Un-expand a needlessly expanded prodn
jmdyck 0933cf9
Editorial: Change [U] to <sub>[U]</sub>
jmdyck 30a37ea
Editorial: "code unit value" -> "numeric value"
jmdyck 81c4c42
Editorial: Change "the code point value of the SV of |HexEscapeSequen…
jmdyck File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think I picked
code point value
, so I could use the same phrase within the complete section (21.2.1.4 Static Semantics: CharacterValue). Only changing it tonumeric value of the code unit
forCharacterEscape :: HexEscapeSequence
looks a bit odd, because also other productions in 21.2.1.4 evaluate to a single code unit.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, CharacterValue returns an integer in the Unicode codespace, which is too big for a single (16-bit) code unit.
Elsewhere in 21.2.1.4, in occurrences of "the code point value of X" (or "X's code point value"), X either literally denotes a code point (e.g. "U+002D (HYPHEN-MINUS)") or is a metavariable whose value is a code point. But
the SV of |HexEscapeSequence|
is not a code point, so I think it would be misleading to use the same formulation.