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.

Sign up for GitHub

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

Jump to bottom

§16.3.5 [cpp.scope] ends in an unmatched "— end note ]" #80

Closed
je4d opened this issue Apr 19, 2013 · 5 comments · Fixed by #141
Closed

§16.3.5 [cpp.scope] ends in an unmatched "— end note ]" #80

je4d opened this issue Apr 19, 2013 · 5 comments · Fixed by #141

Comments

@je4d
Copy link
Contributor

je4d commented Apr 19, 2013

Paragraphs §16.3.5/3-9 contain examples of the preprocessor macro expansion rules, and as such I would expect them all to not be normative text.

It is clear that §16.3.5/3 is not normative, but unclear whether or not §16.3.5/4-9 are normative text as they end in an unmatched — end note ]

To illustrate, without the text of the examples the paragraphs look like this:

3. [Note:
...
— end note]
4.
...
...
...
9.
...
— end note]
@zygoloid
Copy link
Member

I believe the problem here is that there shouldn't be an - end note ] at the end of paragraph 3. In C, paragraphs 3 to 9 are all examples, and in C++98 there is no - end note ] at the end of paragraph 3. The erroneous \exitnote has been there since the first git revision, so I don't know how it came to be there.

je4d added a commit to je4d/cppdraft that referenced this issue May 19, 2013
@je4d
[cpp.scope] Properly mark macro examples as such
75c667f 
fixes cplusplus#80
@je4d je4d mentioned this issue May 19, 2013
Merged
@sdutoit
Copy link
Contributor

sdutoit commented Jul 2, 2013

These should really be examples, not notes. And it might just be best to put each paragraph in an \enterexample ... \exitexample for clarity.

@je4d
Copy link
Contributor Author

je4d commented Jul 2, 2013

On 02/07/13 18:53, Stefanus Du Toit wrote:

These should really be examples, not notes. And it might just be best to
put each paragraph in an |\enterexample ... \exitexample| for clarity.

That's basically what the pull request does

@sdutoit
Copy link
Contributor

sdutoit commented Jul 3, 2013

I should probably have read the pull request! Thought I had. Sorry about that.

@je4d
Copy link
Contributor Author

je4d commented Jul 3, 2013

No worries, ta for merging it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix for issue #80, [cpp.scope] ends in an unmatched "— end note ]" je4d/cppdraft
3 participants
@zygoloid @sdutoit @je4d