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

Sundry typographical issues from BSI #191

Closed
sdutoit opened this issue Sep 20, 2013 · 1 comment
Closed

Sundry typographical issues from BSI #191

sdutoit opened this issue Sep 20, 2013 · 1 comment
Assignees

Comments

@sdutoit
Copy link
Contributor

sdutoit commented Sep 20, 2013

Pattabi Raman contributed these via BSI.

Typographical errors in Chapters 17, 23-26 of N3690

  • add a line-space above §17.3 (page(p) 409);
  • hyphen before “end note]” in §17.3.12 (p-410);
  • full stops needed at §17.3.17 , §17.3.19 , §17.3.21, §17.3.22¸ §17.3.23, §17.3.24, §17.3.25 and §17.3.26 –all in p-411;
  • Is the sentence in §17.3.25 (p-411) probably looking incomplete?
  • full stops needed at §17.3.27 and at §17.3.28 (p-412);
  • a hyphen needed before “end note]” in note 5 of §17.6.1.1 (p-418, fourth line from the bottom row);
  • Opening square bracket ‘[‘ is needed before “Note:” and hyphen before “end note]” in Table 20 of §17.6.3.1 (p-421);
  • Opening square bracket ‘[‘ is needed before “Note:” in Table 22 of §17.6.3.1 (p-421);
  • hyphen before “end note]” in §17.6.5.13 (p-435);
  • In Table 102 (§ 23.2.4) at Complexity: replace “(N has the value…“ by “, where N has the value …” just after the “Nlog(a.size() + N)”;
  • In the same table at Complexity: add a comma before “where N has the …..”
  • either keep or do not keep full stops at “value_comp (*….= false” at § 23.2.5 (p-750);
  • a full stop is needed at assertion of “a.clear()” in Table 103 of § 23.2.5 (p-757);
  • check spacing at “n -th” in Table 103 of § 23.2.5 (p-758);
  • remove a tab spacing to align “const_reference;” at the top of p-781 (§ 23.3.6.1);
  • remove tabs to align “key_type; value_type; key_compare;….” at the bottom of p-809 (§ 23.4.7.1);
  • a hyphen needed before “end example]” in § 24.2.3 (p-841);
  • a hyphen needed before “end example]” at the end of § 24.4.3 (p-850);
  • a hyphen needed before “end note]” at the top of § 24.6.3 (p-868);
  • add a closing brace “)” before “ or binary_op(*(first…” in § 25.3.4 (p-891);
  • a hyphen needed before “end example]” at section 4 of § 26.2 (p-913);
  • a hyphen needed before “end note]” at section 3 of § 26.3.1 (p-914);
  • a hyphen needed before “end example]” at section 9 of § 26.6.2.8 (p-979);
@jwakely
Copy link
Member

jwakely commented Sep 20, 2013

All the hyphens seem to be present already.

jensmaurer added a commit to jensmaurer/draft that referenced this issue Dec 7, 2016
Harmonize the punctuation in complexity requirements where a definition
for N is introduced.
Add a missing closing parenthesis.
Add a full stop.

Fixes cplusplus#191.
@jensmaurer jensmaurer self-assigned this Dec 7, 2016
tkoeppe pushed a commit that referenced this issue Dec 7, 2016
Harmonize the punctuation in complexity requirements where a definition
for N is introduced.
Add a missing closing parenthesis.
Add a full stop.

Fixes #191.
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