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

References to "member subobject" and "base class subobject" on [intro.object]/2 in italics #965

Open
jabelloc opened this issue Nov 3, 2016 · 5 comments
Open

References to "member subobject" and "base class subobject" on [intro.object]/2 in italics #965

jabelloc opened this issue Nov 3, 2016 · 5 comments
Assignees
@jensmaurer
Labels
tiny An issue with a small change; with "cwg" label: can be applied editorially after CWG consent.

Comments

@jabelloc
Copy link

jabelloc commented Nov 3, 2016

[intro.object]/2

Objects can contain other objects, called subobjects. A subobject can be a member subobject (9.2), a base class subobject (Clause 10), or an array element.

The terms member subobject and base class subobject should not be in italics as they are not definitions at this point.

By the same token, the term "member subobject" should be in italics in [class.mem]/4, where it appears (to me at least) to contain the definition of the term.

[class.mem]/4

... [ Note: A non-static data member of non-reference type is a member subobject of a class object (1.8).—end note ]
@jensmaurer
Copy link
Member

Well, we certainly can't introduce a term in a note that we use in normative text elsewhere.

@jensmaurer
Copy link
Member

@zygoloid: I would un-note the note and make that the definition, and remove the (purported) definition of member subobject and base class subobject from 1.8 [intro.object] p2. This does morph a bit of normative text, though. Ok to proceed, or go through CWG?

@jensmaurer jensmaurer added the decision-required A decision of the editorial group (or the Project Editor) is required. label Nov 21, 2016
@jensmaurer jensmaurer added cwg Issue must be reviewed by CWG. and removed decision-required A decision of the editorial group (or the Project Editor) is required. labels Mar 2, 2017
@jensmaurer
Copy link
Member

Editorial meeting consensus: Present to CWG for feedback.

@jensmaurer
Copy link
Member

Proposed changes uploaded to CWG wiki: http://wiki.edg.com/pub/Wg21rapperswil2018/CoreWorkingGroup/cwg-ed965.html

@jensmaurer jensmaurer added the tiny An issue with a small change; with "cwg" label: can be applied editorially after CWG consent. label Apr 12, 2018
@jensmaurer jensmaurer self-assigned this Apr 13, 2018
@jensmaurer
Copy link
Member

CWG in San Diego: Changes are approved.

@jensmaurer jensmaurer removed the cwg Issue must be reviewed by CWG. label Nov 6, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jensmaurer jensmaurer

Labels
tiny An issue with a small change; with "cwg" label: can be applied editorially after CWG consent.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jabelloc @jensmaurer