[ A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z ]

• Wannabes, Pathetic ... [9.9]
• Wannabes: smoking out people who pretend to know C++ ... [6.14]
• Wars ... [27.1]
• Water vehicle (example) ... [25.5], [25.7]
• Weenie ("Techie Weenie") ... [6.5], [9.9]
• What to catch (see also under Exceptions) ... [17.13]
• What to throw (see also under Exceptions) ... [17.12]
• When in Rome, do as the Romans ... [17.14]
• Where do I start? ... [29.2]
• Which operators can be overloaded (see also Operator overloading) ... [13.5]
• Which operators should be overloaded (see also Operator overloading) ... [13.8]
• while (std::cin >> foo) and std::istream (input/output) ... [15.4]
• Whipping boy for the weak (see also under Exceptions) ... [17.5]
• Whitespace standards ... [29.10]
• Wild pointer ... [12.2], [16.25], [34.6]
• Windows, Microsoft
  • Binary mode for opening streams ... [15.12]
  • Binary mode for std::cin and std::cout ... [15.13]
  • Newsgroups specializing in ... [5.9]
  • OS-specific questions/answers ... [40.5]
• Writer/writer conflicts; Multi-threading and ... [36.12]
• Wrong mindset (see also under Exceptions) ... [17.6], [17.7]
• Wrong/naive beliefs
  • Always name numeric literals ... [29.11]
  • Friendship breaks encapsulation ... [14.2]
  • inline functions always improve performance ... [9.3]
  • Methods always better than friend-functions ... [15.9]
  • Multi-line macros simply use {...} ... [39.5]
  • Never use #define ... [29.7]
  • Never use multiple-inheritance ... [25.2], [25.3]
  • One size fits all ... [25.6]
  • protected data is evil ... [19.8]
  • "Always" and "Never" rules ... [23.3]
  • "Evil" things should never be used ... [6.15]
  • Software has rules that always apply ... [6.16], [17.8], [21.8], [23.4], [25.5]
  • There exists a purely technical definition of "good" ... [6.17]
  • Token-pasting doesn't require two levels of macros ... [39.6]
• WWW sites of this document ... [2.1]