Errata for Understanding and Using C Pointers
Submit your own errata for this product.
The errata list is a list of errors and their corrections that were found after the product was released. If the error was corrected in a later version or reprint the date of the correction will be displayed in the column titled "Date Corrected".
The following errata were submitted by our customers and approved as valid errors by the author or editor.
Color Key: Serious Technical Mistake Minor Technical Mistake Language or formatting error Typo Question Note Update
| Version |
Location |
Description |
Submitted By |
Date Submitted |
Date Corrected |
| Safari Books Online |
1
chapter 1, "pointers and memory" section, right before "declaring pointers" subsection |
uh, the safari version of this book doesn't have pages (so, sorry, no page number or succinct location).
in the *undefined* section it says "A list of *unspecified* behavior can be found at CERT Secure Coding Appendix CC." (emphasis mine)
it should say, "A list of *undefined* behavior can be found at CERT Secure Coding Appendix CC" (as the CERT Secure Coding Appendix CC is entitled "Undefined Behavior" and "unspecified behavior" was covered in the previous paragraph).
Note from the Author or Editor:
In Chapter 1, Introduction, towards the end of the section titled, "Why You Should Become Proficient with Pointers", the third bullet contains the following sentence:
"A list of unspecified behavior can be found at CERT Secure Coding Appendix CC."
It should read:
"A list of undefined behavior can be found at CERT Secure Coding Appendix CC."
|
unlisted |
May 16, 2013 |
|
| Safari Books Online |
1
Ch 1 -> "Common Uses of Pointers" -> "Constants and Pointers" -> "Pointers to a Constant" |
In discussing pointers to constants (meaning pointers that point to values that cannot be changed [at least by way of the pointer]), it is said:
"The pointer thinks it is pointing to a constant integer; therefore, it does allow the modification of the integer using the pointer."
It should say:
"The pointer thinks it is pointing to a constant integer; therefore, it does *not* allow the modification of the integer using the pointer." (Emphasis mine.)
Just a small typo.
Note from the Author or Editor:
Change:
"The pointer thinks it is pointing to a constant integer; therefore, it does allow the modification of the integer using the pointer."
To read:
"The pointer thinks it is pointing to a constant integer; therefore, it does not allow the modification of the integer using the pointer." |
unlisted |
May 18, 2013 |
|
| PDF, Mobi |
Page 61
Last paragraph |
"Passing a pointer to the object means the object does *not*.... "
(Last sentence)
The page number is from the PDF format of the book.
Note from the Author or Editor:
Change:
"Passing a pointer to the object means the object does have to
be copied, and we can access the object through the pointer."
To:
"Passing a pointer to the object means the object does not have to
be copied, and we can access the object through the pointer." |
Amit Saha |
May 11, 2013 |
|
|
| |
