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

Editorial fix in [namespace.def] #154

Closed
wants to merge 1 commit into from
Closed

Conversation

FrankHB
Copy link
Contributor

@FrankHB FrankHB commented Jul 10, 2013

An identifier makes an entity defined only through several known kind of declarations. Here the word "defined" would make "typedef int X; namespace X{}" unintentionally well-formed, because the name "X" is introduced by a non-definition(typedef declaration) and nothing named "X" is defined previous the namespace definition.

An identifier makes an entity defined only through several known kind of declarations. Here the word "defined" would make "typedef int X; namespace X{}" unintentionally well-formed, because the name "X" is introduced by a non-definition(typedef declaration) and nothing named "X" is defined previous the namespace definition.
@sdutoit
Copy link
Contributor

sdutoit commented Sep 27, 2013

This is a change to normative wording that changes its meaning. It may be a fine change, but it's not an editorial issue. Perhaps @zygoloid could add a core issue.

@sdutoit sdutoit closed this Sep 27, 2013
@zygoloid
Copy link
Member

zygoloid commented Oct 5, 2013

[basic.scope.declarative]p4 makes a program ill-formed if there's a prior declaration of the name that isn't a namespace, but I think there is something interesting going on here: the intent of this "shall [not] have been previously declared" wording in p2 and p3 seems to be to determine which of the two grammar rules should be used, but "shall" is the wrong word to use in p2, because the program is not ill-formed if we get there and "identifier" has previously been defined as a namespace. I'll submit a core issue on that.

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 this pull request may close these issues.

None yet

3 participants