Errata

Fluent C

Errata for Fluent C

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
Page Chapter 2. Returning Error Information
In the first "Running Example" Under the code example, right before the "Return Status Codes" section

possibility is written as "possibilitym"

Note from the Author or Editor:
Typo: possibility is written as "possibilitym"
That is in the first "Running Example" Under the code example, right before the "Return Status Codes" section
--> I already fixed it in my book on the ATLAS platform.

 Bill  Jul 07, 2023 
Page General throughout
All "Known uses"

In the "Known uses" section, there are many references to real-world code that uses the concepts discussed in the chapter. As a reader, I want to check the actual code for the usage. However, there are currently 2 minor issues trying to find the actual code:
1. The file in which the function exists is not mentioned, making it a bit tricky to find sometimes, and
2. more importantly, the author doesn't mention _when_ he checked the code. For example, on page 21, the author mentions the "cap_open_socket" function which uses "lazy-evaluation". This is not true in the latest code base (2023-11-17). However, it was true a couple of years ago. It would really help if we get a timestamp for when the author accessed the code, so we can go back to the same point in history.

Note from the Author or Editor:
Request to add the date when the code examples of the book were accessed and request to add information about the function names in these code examples.

I already added that info in the ATLAS repository of my book

 Jonathan  Nov 16, 2023 
Page Chapter 1 - Cleanup Record
Throughout the section

The author talks about "lazy evaluation", when actually showing "short-circuit".

Note from the Author or Editor:
In chapter 1, all occurrances of the phrase "lazy evaluation" should be replaced with "short-circuit evaluation.

I already fixed that in the ATLAS main branch of my book.

 Jonathan  Nov 16, 2023 
Page 7
3rd paragraph, code

void mainFunctionality()
{
//implementation goes here
}

I think it should be

void mainFunctionality(char* buffer)
{
//implementation goes here
}

Note from the Author or Editor:
A code example contained a syntax error. I already updated that in the ATLAS repository of my book.

 Yeo Kai Wei  Dec 05, 2023 
Page 85
Bottom 2 lines

#define MAX_ELEMENTS 20;
#define ELEMENT_SIZE 255;

The ';' are unnecessary and will not allow the code to compile.

Note from the Author or Editor:
One of the code snippets has a mistake and would not compiler. I already fixed that mistake in the ATLAS repository.

 yeokaiwei  Dec 07, 2023