Appendix A: Language Reference Tables

This appendix gathers compact reference tables that you can consult quickly while working. They summarize essential facts without long explanation. Earlier chapters give full detail; the tables here provide fast reminders during coding or review.

Keywords and reserved identifiers

C++ reserves a small core of keywords for language features and implementation needs. These names cannot be used for your own identifiers. Some are contextual and appear only in templates or special constructs. The list below reflects the common set from current C++ standards.

Core keywords

The following table lists the fundamental keywords that appear in code across the language’s main features. They map to control flow, declarations, types, and basic operators.

Operator precedence and associativity

Operator precedence determines how expressions bind when parentheses are absent. Associativity resolves ties at the same level. When expressions become dense, add parentheses for clarity even when precedence rules cover the case.

Precedence table

The following table shows a compact precedence ladder. Rows near the top bind more tightly than rows near the bottom. The associativity column explains the direction rules when operators share a level.

Numeric limits and sizes

The exact sizes of integer and floating point types vary by platform, but common implementations follow patterns. The table provides typical values from platforms that use 8 bit bytes and two’s complement integers. Always confirm with std::numeric_limits<T> at compile time if your code depends on exact ranges.

Common sizes

The table shows representative bit widths and ranges, not strict guarantees. Your platform may differ.

Compiler flag crib sheet

Compilers offer flags that control standards, warnings, optimization, sanitizers, and debugging. The tables here list commonly used flags for GCC, Clang, and MSVC. Exact spellings may vary slightly by version.

Language and warnings

Choose a standard version explicitly and enable strong warnings during development. These flags help catch mistakes before runtime.

Optimization and debugging

Switch between optimization levels depending on context. Fast builds use no optimization; release builds use higher levels. Include debugging information during development.

Sanitizers

Sanitizers catch memory errors, undefined behavior, and threading races. Use them in CI and during development to prevent subtle bugs from reaching production.