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

Inconsistent formatting of "public" and "inline" in sentences #106

Closed
sdutoit opened this issue May 9, 2013 · 3 comments
Closed

Inconsistent formatting of "public" and "inline" in sentences #106

sdutoit opened this issue May 9, 2013 · 3 comments
Assignees
@jensmaurer
Labels
formatting

Comments

@sdutoit
Copy link
Contributor

sdutoit commented May 9, 2013

There are a bunch of inconsistencies around whether to \tcode public and inline, e.g. in "public inline member function" throughout the standards text.
@jensmaurer
Copy link
Member

As far as I understand, the rule is to use \tcode{} when referring to syntax appearing in a program, and normal text when we refer to an attribute of a function. For example, a function can be inline even if it's not declared with the inline keyword (e.g. defined in-class). And public (the keyword) isn't even part of the function declaration.

@jensmaurer jensmaurer added the decision-required A decision of the editorial group (or the Project Editor) is required. label Dec 8, 2016
@jensmaurer
Copy link
Member

Editorial meeting consensus: We agree that we use \tcode when referring to syntax, and otherwise not. We should add that to the style guide on the wiki.

@jensmaurer jensmaurer removed the decision-required A decision of the editorial group (or the Project Editor) is required. label Mar 2, 2017
@zygoloid zygoloid mentioned this issue Mar 2, 2017
Closed
@jensmaurer jensmaurer mentioned this issue Mar 2, 2017
Closed
@jensmaurer
Copy link
Member

Wiki page was updated.

jensmaurer added a commit to jensmaurer/draft that referenced this issue Mar 28, 2017
@jensmaurer
Do not use \tcode for non-syntax.
f75e6d9 
This applies to inline, public, protected, private, and friend.

Fixes cplusplus#106.
@jensmaurer jensmaurer mentioned this issue Mar 28, 2017
Merged
@jensmaurer jensmaurer self-assigned this Mar 28, 2017
jensmaurer added a commit to jensmaurer/draft that referenced this issue Jul 21, 2017
@jensmaurer
Do not use \tcode for non-syntax.
097edc7 
This applies to inline, public, protected, private, and friend.

Fixes cplusplus#106.
jensmaurer added a commit to jensmaurer/draft that referenced this issue Nov 12, 2017
@jensmaurer
Do not use \tcode for non-syntax.
4bbb0f9 
This applies to inline, public, protected, private, and friend.

Fixes cplusplus#106.
zygoloid pushed a commit that referenced this issue Nov 12, 2017
@jensmaurer @zygoloid
Do not use \tcode for non-syntax.
3b938b0 
This applies to inline, public, protected, private, and friend.

Fixes #106.
AaronBallman pushed a commit to AaronBallman/draft that referenced this issue Nov 15, 2017
@jensmaurer
Do not use \tcode for non-syntax.
637ff41 
This applies to inline, public, protected, private, and friend.

Fixes cplusplus#106.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jensmaurer jensmaurer

Labels
formatting
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@sdutoit @jensmaurer