The Rook's Guide to C++
TeX C++ C Shell
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
diagrams Stick a fork in it - here's version 1.0! Nov 26, 2013
graphics Copyedits to STL, Strings. Added License page w/graphics Jul 27, 2013
src Address Issue #31 Oct 28, 2015
.gitignore Stick a fork in it - here's version 1.0! Nov 26, 2013
README.md Cleaning up unneeded files Dec 2, 2013
chap_advancedarith.tex Finalizing edits Nov 17, 2013
chap_arithmetic.tex Some updates to file IO, other misc fixes Apr 27, 2014
chap_arrays.tex Finalizing edits Nov 17, 2013
chap_assignments.tex Continuing finalization: through Ch. 8 Nov 15, 2013
chap_classes.tex Stick a fork in it - here's version 1.0! Nov 26, 2013
chap_comments.tex A fix to comments chapter & page layout Dec 30, 2013
chap_conditionals.tex Corrected a stray `:` for #22 Nov 28, 2013
chap_constants.tex Final updates (?) Nov 26, 2013
chap_datatypes.tex Stick a fork in it - here's version 1.0! Nov 26, 2013
chap_dynamic.tex Finalizing edits Nov 17, 2013
chap_exceptions.tex Initial commit Jul 17, 2013
chap_file_io.tex Some updates to file IO, other misc fixes Apr 27, 2014
chap_functions.tex Stick a fork in it - here's version 1.0! Nov 26, 2013
chap_history.tex Lots of various changes Nov 12, 2013
chap_input.tex Finalizing edits Nov 17, 2013
chap_loops.tex Finalizing edits Nov 17, 2013
chap_memory.tex Initial commit Jul 17, 2013
chap_output.tex Correct wording around code Oct 28, 2015
chap_pointers.tex Finalizing edits Nov 17, 2013
chap_preproc.tex Substantial update (by Hartley) to Preprocessors Apr 27, 2014
chap_problems.tex Stick a fork in it - here's version 1.0! Nov 26, 2013
chap_sampleprogram.tex Initial commit Jul 17, 2013
chap_separate.tex Finalizing edits Nov 17, 2013
chap_stl.tex Some updates to file IO, other misc fixes Apr 27, 2014
chap_strings.tex Final updates (?) Nov 26, 2013
chap_testing.tex Initial commit Jul 17, 2013
chap_types.tex Initial commit Jul 17, 2013
chap_userdefined.tex Initial commit Jul 17, 2013
chap_variables.tex Stick a fork in it - here's version 1.0! Nov 26, 2013
cpp.lol Arrays content updated, readme created Jul 23, 2013
cpp.tcp Some updates to file IO, other misc fixes Apr 27, 2014
cpp.tex Some updates to file IO, other misc fixes Apr 27, 2014
cpp.tps A fix to comments chapter & page layout Dec 30, 2013
kickstarters.tex All chapters' source material finished Nov 5, 2013
utils-commands.tex Misc. fixes Nov 15, 2013
utils-listings.tex Reduced the amount of whitespace below listings Nov 15, 2013

README.md

The Rook's Guide to C++

Here are some basic expectations for getting the .tex files in publication shape:

  • Each topic has its own .tex file - for right now they're all organized as digestible mini-chapters, though I expect them to merge and evolve later on.

  • The cpp.tex file is the core of the project, and the place where all the chapters are inserted via \input{}

  • Chapter \sections should be designated with \LevelD{My section} and \subsections with \LevelE{My subsection}

  • Bits of code and symbols within a sentence should be placed within a \Code{…}. So should program output, which should appear on its own line.

  • Code listings that stand on their own (and pseudocode) should be put in

      \noindent\begin{minipage}{\linewidth}\begin{lstlisting}
      /* Code */
      \end{lstlisting}\end{minipage}
    
  • Important terms should be placed within \Keyword{...}. This indexes them automatically.

  • Each chapter should have the following sections, in this order:

    • \LevelD{Review Questions}

    • \LevelD{Review Answers}

    • \LevelD{Further Reading}

  • Write each sentence on a separate line. This helps with managing versions. It's harder to look at but easier to maintain.

  • Wrap URLs in \url{...}

  • Fork your own branch, and we'll pull your changes gradually into the master branch

  • Thanks for your help! Feel free to contact me at jeremyhansen@acm.org, skype:jah_vt, or if it's more appropriate to add it as a GitHub issue, feel free to put it there.