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

Consider changing title of [fs.err.report] #671

Closed
jwakely opened this issue Mar 31, 2016 · 3 comments
Closed

Consider changing title of [fs.err.report] #671

jwakely opened this issue Mar 31, 2016 · 3 comments

Comments

@jwakely
Copy link
Member

jwakely commented Mar 31, 2016

Both 27.5.6.5 [error.reporting] and 27.10.7 [fs.err.report] have the title "Error reporting". Maybe not a problem if the context is always clear, or references to Error reporting always include a cross-reference to the correct subclause.

@burblebee
Copy link
Contributor

I don't like the word "report" itself. Errors aren't being "reported", but "handled". But yes, having 2 sections with the same name is confusing, even with xrefs.

@jensmaurer
Copy link
Member

Depending on the outcome of #1242, it seems we might have lots more subheadings with the same title, only differentiated by their parent headings.

Put differently, when employing "short" subheadings, it's probably unavoidable to get duplicates in different parts of the heading tree.

I suggest NAD here (and those who wish to change "reporting" to something else should open a new issue; it seems to me this is really about reporting errors to the application).

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

Editorial meeting consensus: Do not try to identify sections by heading; use labels instead.

@jensmaurer jensmaurer removed the decision-required A decision of the editorial group (or the Project Editor) is required. label Mar 2, 2017
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

No branches or pull requests

3 participants