jlospinoso/ccc issues and pull requests

#100 - Page 367: Listing 11-19 refers to non-existant identifier "my_alloc".

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 1 comment

#100 - Page 367: Listing 11-19 refers to non-existant identifier "my_alloc".

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 1 comment

#99 - Page 342 and 344 (and elsewhere): The way you are using Catch.hpp will cause massive compilation slowdowns for anyone who mimics you.

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 3 comments

#99 - Page 342 and 344 (and elsewhere): The way you are using Catch.hpp will cause massive compilation slowdowns for anyone who mimics you.

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 3 comments

#98 - Pages 295 and 296: Getting an unexpected behavior when try to capture local variable

Issue - State: open - Opened by carpajr almost 5 years ago - 9 comments

#98 - Pages 295 and 296: Getting an unexpected behavior when try to capture local variable

Issue - State: open - Opened by carpajr almost 5 years ago - 9 comments

#97 - Page 402: boost::convert and boost::converter instead of boost::numeric::converter

Issue - State: closed - Opened by cetetesoft almost 5 years ago - 3 comments

#97 - Page 402: boost::convert and boost::converter instead of boost::numeric::converter

Issue - State: closed - Opened by cetetesoft almost 5 years ago - 3 comments

#96 - Page 359: "Listing 11-12" should read "Listing 11-13"

Issue - State: closed - Opened by cetetesoft almost 5 years ago - 1 comment

#96 - Page 359: "Listing 11-12" should read "Listing 11-13"

Issue - State: closed - Opened by cetetesoft almost 5 years ago - 1 comment

#95 - Page 158: char instead of size_t (listing 6-12)

Issue - State: closed - Opened by cetetesoft almost 5 years ago - 1 comment

#95 - Page 158: char instead of size_t (listing 6-12)

Issue - State: closed - Opened by cetetesoft almost 5 years ago - 1 comment

#94 - Page 146: Listing 5-13 should include 5-11 instead of 5-10

Issue - State: closed - Opened by cetetesoft almost 5 years ago - 2 comments

#94 - Page 146: Listing 5-13 should include 5-11 instead of 5-10

Issue - State: closed - Opened by cetetesoft almost 5 years ago - 2 comments

#93 - Page 41: %zu is a better format specifier for size_t than %zd

Issue - State: closed - Opened by delan almost 5 years ago - 1 comment

#93 - Page 41: %zu is a better format specifier for size_t than %zd

Issue - State: closed - Opened by delan almost 5 years ago - 1 comment

#92 - Page 41: typo <stddef> should read <cstddef>

Issue - State: closed - Opened by delan almost 5 years ago - 1 comment

#92 - Page 41: typo <stddef> should read <cstddef>

Issue - State: closed - Opened by delan almost 5 years ago - 1 comment

#91 - There's an error on the errata page itself. Wrong/meaningless: p. 277 Exercise 9-3, "template " should read "template "

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 1 comment

#91 - There's an error on the errata page itself. Wrong/meaningless: p. 277 Exercise 9-3, "template " should read "template "

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 1 comment

#90 - Page 277: In exercise 9-1, the function call to "print" should be "printf".

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 1 comment

#90 - Page 277: In exercise 9-1, the function call to "print" should be "printf".

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 1 comment

#89 - Link to East End Functions is incorrect

Issue - State: closed - Opened by ellowrath almost 5 years ago - 1 comment

#89 - Link to East End Functions is incorrect

Issue - State: closed - Opened by ellowrath almost 5 years ago - 1 comment

#88 - Page 261: Non-existant variable "l" (letter L) is used in code example. Should be "len" instead.

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 2 comments

#88 - Page 261: Non-existant variable "l" (letter L) is used in code example. Should be "len" instead.

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 2 comments

#87 - Page 258: Term choice "specifiers" in bullet list differs from term choice "modifiers" in lambda syntax example.

Issue - State: closed - Opened by WraithGlade almost 5 years ago

#87 - Page 258: Term choice "specifiers" in bullet list differs from term choice "modifiers" in lambda syntax example.

Issue - State: closed - Opened by WraithGlade almost 5 years ago

#86 - Page 155: Misplaced circled code numbers

Issue - State: closed - Opened by tcflanagan almost 5 years ago

#86 - Page 155: Misplaced circled code numbers

Issue - State: closed - Opened by tcflanagan almost 5 years ago

#85 - Page 159: Apparent contradiction between text and Listing 6-13

Issue - State: closed - Opened by tcflanagan almost 5 years ago - 1 comment

#85 - Page 159: Apparent contradiction between text and Listing 6-13

Issue - State: closed - Opened by tcflanagan almost 5 years ago - 1 comment

#84 - Page 200: The text states that the address of int x prints 0, which is wrong.

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 1 comment

#84 - Page 200: The text states that the address of int x prints 0, which is wrong.

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 1 comment

#83 - Pages 187 and 188: In the example code, on page 187 operator+ throws runtime_error but in use on page 188 the catch only catches overflow_error.

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 1 comment
Labels: duplicate

#83 - Pages 187 and 188: In the example code, on page 187 operator+ throws runtime_error but in use on page 188 the catch only catches overflow_error.

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 1 comment
Labels: duplicate

#82 - Page 175: The text refers to a non-existant exception type named "out_of_bounds".

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 1 comment

#82 - Page 175: The text refers to a non-existant exception type named "out_of_bounds".

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 1 comment

#81 - Page 167: Description of concept Averagable says it uses two type traits when it actually only uses one.

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 1 comment

#81 - Page 167: Description of concept Averagable says it uses two type traits when it actually only uses one.

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 1 comment

#80 - Page 149: Martha Stewart quote at top of chapter 6 is misquoted. It has a typo.

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 1 comment

#80 - Page 149: Martha Stewart quote at top of chapter 6 is misquoted. It has a typo.

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 1 comment

#79 - Page 137 of ebook: Hyperlinks to Chapters 20 and 21 of "The C + + Programming Language" (4th Edition, by Bjarne Stroustrup) link instead to internal C++ Crash Course chapters.

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 1 comment

#79 - Page 137 of ebook: Hyperlinks to Chapters 20 and 21 of "The C + + Programming Language" (4th Edition, by Bjarne Stroustrup) link instead to internal C++ Crash Course chapters.

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 1 comment

#78 - Page 112 refers to a non-existant function "fn()" in the text.

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 1 comment

#78 - Page 112 refers to a non-existant function "fn()" in the text.

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 1 comment

#77 - Pages 108, 110, and 111: The given console output of SimpleStringOwner on page 111 is wrong relative to the prior code.

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 1 comment

#77 - Pages 108, 110, and 111: The given console output of SimpleStringOwner on page 111 is wrong relative to the prior code.

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 1 comment

#76 - Page 110: SimpleString is referred to incorrectly as being of type "string" in the parenthetical sentence.

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 1 comment

#76 - Page 110: SimpleString is referred to incorrectly as being of type "string" in the parenthetical sentence.

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 1 comment

#75 - Page 100: Explanation of exception inheritance hierarchy handling in catch blocks is wrong.

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 1 comment

#75 - Page 100: Explanation of exception inheritance hierarchy handling in catch blocks is wrong.

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 1 comment

#74 - Page 91 and 92: Threshold value in condition "waste_heat > 10000" and the value mentioned later in the text are not the same.

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 2 comments

#74 - Page 91 and 92: Threshold value in condition "waste_heat > 10000" and the value mentioned later in the text are not the same.

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 2 comments

#73 - Contrary to how it is worded, listing 2-12 does not show a "conversion" to uppercase.

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 2 comments

#73 - Contrary to how it is worded, listing 2-12 does not show a "conversion" to uppercase.

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 2 comments

#72 - Likely missing quotations around unicode English and Chinese examples on/near page 46.

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 1 comment

#72 - Likely missing quotations around unicode English and Chinese examples on/near page 46.

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 1 comment

#71 - Note box about expressions on/near page 44 comes across as disconnected from context.

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 1 comment

#71 - Note box about expressions on/near page 44 comes across as disconnected from context.

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 1 comment

#70 - Explaination of array type is ambiguously worded on/near page 42 in ebook.

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 1 comment

#70 - Explaination of array type is ambiguously worded on/near page 42 in ebook.

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 1 comment

#69 - Typo in size_t description section on/near page 41 of ebook (etc)

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 1 comment

#69 - Typo in size_t description section on/near page 41 of ebook (etc)

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 1 comment

#68 - Consider adding "standard" into std pronunciation note box as another option.

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 1 comment

#68 - Consider adding "standard" into std pronunciation note box as another option.

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 1 comment

#67 - Description of unary negation operator should probably have "bool" qualifier added to sentence.

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 1 comment

#67 - Description of unary negation operator should probably have "bool" qualifier added to sentence.

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 1 comment

#66 - The suggestion to avoid using cstdint seems maybe ill advised.

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 1 comment

#66 - The suggestion to avoid using cstdint seems maybe ill advised.

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 1 comment

#65 - Some grammatical errors in the text after the int type table on/near page 32 in ebook.

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 1 comment

#65 - Some grammatical errors in the text after the int type table on/near page 32 in ebook.

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 1 comment

#64 - Possible typo in the "fundamental types" paragraph on/near page 31 of ebook.

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 1 comment

#64 - Possible typo in the "fundamental types" paragraph on/near page 31 of ebook.

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 1 comment

#63 - Very subjective/pedantic point: phrasing of "search on your error messages online" maybe a bit odd.

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 1 comment

#63 - Very subjective/pedantic point: phrasing of "search on your error messages online" maybe a bit odd.

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 1 comment

#62 - The wording of part of your description of comments is a bit wrong.

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 1 comment

#62 - The wording of part of your description of comments is a bit wrong.

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 1 comment

#61 - Pedantic point: the note box about the use of "--snip--" should maybe come earlier in the book or not at all.

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 1 comment

#61 - Pedantic point: the note box about the use of "--snip--" should maybe come earlier in the book or not at all.

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 1 comment

#60 - Possible that you intended "INPUT-OUPUT" instead of "INPUT OUTPUT" on note box on page 18

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 1 comment

#60 - Possible that you intended "INPUT-OUPUT" instead of "INPUT OUTPUT" on note box on page 18

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 1 comment

#59 - Possible omission of a word in the note box for printf.

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 1 comment

#59 - Possible omission of a word in the note box for printf.

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 1 comment

#58 - A pedantic point about the else block "always" executing... (not a big deal)

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 1 comment

#58 - A pedantic point about the else block "always" executing... (not a big deal)

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 1 comment

#57 - One of the sentences in the basic if/else-if/else condition section is confusingly worded.

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 1 comment

#57 - One of the sentences in the basic if/else-if/else condition section is confusingly worded.

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 1 comment

#56 - Another missing space in ebook, near page 4 location 1089 in ebook

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 1 comment

#56 - Another missing space in ebook, near page 4 location 1089 in ebook

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 1 comment

#55 - There's a missing space in a code example, near Loc 1003 in ebook.

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 2 comments

#55 - There's a missing space in a code example, near Loc 1003 in ebook.

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 2 comments

#54 - A code example reference number appears to be wrong, near Loc 1003 in ebook.

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 1 comment

#54 - A code example reference number appears to be wrong, near Loc 1003 in ebook.

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 1 comment

#53 - Probably a typo: "mannie_service" vs "make_sentient" near Loc 660 in ebook.

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 1 comment

#53 - Probably a typo: "mannie_service" vs "make_sentient" near Loc 660 in ebook.

Issue - State: closed - Opened by WraithGlade almost 5 years ago - 1 comment

#52 - strcpy_s in listing 4-30 should be std::strcpy

Issue - State: closed - Opened by JLospinoso almost 5 years ago

#52 - strcpy_s in listing 4-30 should be std::strcpy

Issue - State: closed - Opened by JLospinoso almost 5 years ago

#51 - page 336: Q re IServiceBusMock

Issue - State: closed - Opened by thederz almost 5 years ago - 1 comment

#51 - page 336: Q re IServiceBusMock

Issue - State: closed - Opened by thederz almost 5 years ago - 1 comment

GitHub / jlospinoso/ccc issues and pull requests