Similar to #17, we have blurry diagrams.

I've recently discovered TikZ, which I believe will be a fantastic replacement for the open office diagram / graphics file method.

http://www.texample.net/tikz/examples/simple-flow-chart/

...needing to create a temporary variable and such.

Have to mention that you need a C++11-capable compiler

The TeX file seems to have a lot of contents that are very specific and relatively constant.

For example,

• Kickstarter Contributors
• Hyphenation training data
• Some of the settings

Ideally, at least in my opinion, the main TeX file should be like

\documentclass[...]{...}
\title{..}
% Other base stuff that goes on the front page
% Include settings tex here
% Include new commands tex here

% Finally start the content!
\begin{document}

% Include some content preludes here

\include{chapter1.tex}
...
\include{chapter20.tex}
% include settings for back matter
\include{backmatter.tex}

To me, this makes it easier to comprehend and to edit. This is not to say to force things like \LevelA to be separate from the chapter tex's.
This way, it also means that records on specific parts are easier to track over time.

Let the preprocessor do the work for us here, we don't write all of our classes in main.cpp for a reason 😄

(currently) Figure 14.1 where it says void myFunction (int parameter); has bad contrast and is hard to ready.

I suggest a lighter grey be used.

Jeremy,
I noticed you put up some figures today/last night, and I just got to adding some as well.

Currently we have

LaTeX Warning: Reference `fig-stringfind' on page 62 undefined on input line 12
LaTeX Warning: Reference `fig-netbeans-syntax-error' on page 91 undefined on in
LaTeX Warning: Reference `fig_studentsmap' on page 146 undefined on input line 

missing.

I just added if and if-else diagrams in the conditional chapter. Please review them and give feedback.

include

using namespace std;

int main()
{
double num = 3.14159265;
cout.precision(2);
cout << num << endl;
}

Prints 3.1 instead of 3.14 since it is using the default floating-point notation.

Figure 11.1 shows a string in array format, I believe that it should also include an 11th cell which has \0 or \NUL or something like that. (preferably \0).

Although a very tiny detail, we shouldn't make strings magical by hiding how they tell the end of a string.

For example, in C-languages, a string is usually null terminated, though in other languages like python, the first memory cell is usually a word (int32 or int64 depending on platform) which has the count for how large the rest of the sequence of bytes / characters / entries will be. Note, that this is not exactly how python works, but is the general concept for most languages that are more recent.

However, an iterator will not go over this "11th" cell.

We mention arrays and such, but never show that a string can actually be accessed like an array with the operator [] that strings have.

It looks like open office did the lame thing and just put a bitmap inside of the exported PDF.

It is hard to read and isn't crisp like the other diagrams.

I would also advise in using a monospace font in those diagrams for the code examples like int *

Binaries such as the pdf really ought not to be put in the repository. It would be best to have a periodically uploaded document to share, rather than clutter the repository with these [artifacts](http://en.wikipedia.org/wiki/Artifact_(software_development\)).

Also, log files and the such really don't have a place in the repo, since it also classifies as an artifact and changes per run in any arbitrary environment.

I'd like to make another branch within this repository to make sure that it can be pulled, generated and so forth, then submit a merge request at the review of another to try on their end.

Lines 103 - 109

Perhaps adding an explanation of why the expression is empty -- because of the stray ; -- would be good (Normally I'd fork the file, but I won't for something this minor)

Cheers
Craig

I'd like to assign myself these chapters so that I can do them without worry of duplicate work

I will be traveling via car for a good while, so I thought I'd take on these chapters while I have no internet next week.

A reviewer commented this, and I know this to be true.

"In table 9.1 of chapter 9 "Data types and Conversion" you wrote that the char data type ranges from -128 to 127, but that's not true, because the standard doesn't say that a char is signed or unsigned, it depends on the implementation. A char can be an unsigned char and in that case it will range from 0 to 255."

djrt;k,lypb peopouiu puri jn599500 tfrguoiymp## ## _
c;
c:>md ram_
c;\cd ram
c;|ravi