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

[dcl.pre] paragraphs are in a strange order #338

Closed
zygoloid opened this issue Jun 22, 2014 · 1 comment · Fixed by #4462
Closed

[dcl.pre] paragraphs are in a strange order #338

zygoloid opened this issue Jun 22, 2014 · 1 comment · Fixed by #4462
Assignees

Comments

@zygoloid
Copy link
Member

First we have "the simple-declaration is divided into three parts".
Then a digression on attribute-declarations and scopes.
Then back to simple-declarations again.
Then a digression on static_assert-declarations and empty-declarations.
Then, with no introduction or explanation, some words about init-declarators, and about decl-specifier-seq's. That's clearly supposed to be related to the prior stuff about simple-declarations, but we're too far away for that to be a reasonable implied context.
Oh, then a lie: "Syntactic components beyond those found in the general form of declaration are added to a function declaration to make a function-definition." This means to say "beyond those found in the general form of a simple-declaration"; a function-definition is one of the possibilities in the general form of "declaration".
And then back to decl-specifier-seq's again.

This is a mess and should be fixed.

Related: we should check which of these simple-declaration rules should also apply to function-definitions and member-declarations, and suggest to core that any discrepancies be fixed.

@jensmaurer jensmaurer changed the title [dcl.dcl] paragraphs are in a strange order [dcl.pre] paragraphs are in a strange order Jan 12, 2021
@jensmaurer jensmaurer self-assigned this Jan 12, 2021
@opensdh
Copy link
Contributor

opensdh commented Feb 16, 2021

Before this is closed (and thus vanished): has anyone done the check in the last sentence of the issue description?

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

Successfully merging a pull request may close this issue.

3 participants