Skip to content
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

inconsistent formatting for "underlying type" #330

Closed
burblebee opened this issue Jun 18, 2014 · 2 comments
Closed

inconsistent formatting for "underlying type" #330

burblebee opened this issue Jun 18, 2014 · 2 comments

Comments

@burblebee
Copy link
Contributor

"underlying type" is defined in basic.tex 3.9.1 [basic.fundamental] p5, is used throughout the spec, yet is formatted as a \term{} only in declarations.tex 7.2 [dcl.enum] p9.

@burblebee burblebee added the cwg label Jun 18, 2014
@burblebee burblebee changed the title intended definition of "underlying type" is unclear inconsistent formatting for "underlying type" Jun 18, 2014
@burblebee burblebee removed the cwg label Jun 18, 2014
@burblebee
Copy link
Contributor Author

While this issue was opened to address all occurrences of "underlying type" in the spec, we're narrowing its scope to just the issues in 3.9.1 and 7.2. Issue #391 was opened for some of the remaining occurrences, and the rest will be dropped from this issue entirely.

@jensmaurer
Copy link
Member

I'd like to point out that "underlying type" in 3.9.1 refers to the base type for wchar_t, char16_t, and char32_t, whereas "underlying type" in 7.2p9 talks about the underlying type of an enumeration. These two definitions, strictly speaking, have nothing to do with each other.

Am I understanding correctly that this editorial issue strives to add italics to the introduction of the term "underlying type" for enumerations in 7.2p5 "Each enumeration also has an underlying
type." ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants