cc: #include "b.h" void f(B*); void f(void*); void test(D* x) { f(x); } // calls f(B*) If the #include was replaced with forward decls for B and D, test() would call f(void*). • Forward declaring multiple should be included as: #include "base/logging.h" In dir/foo.cc or dir/foo_test.cc, whose main purpose is to implement or test the stuff in dir2/foo2.h, order your includes as follows: 1. dir2/foo2.h. preferred ordering, if dir2/foo2.h omits any necessary includes, the build of dir/foo.cc or dir/foo_test.cc will break. Thus, this rule ensures that build breaks show up first for the people working on these

well-established conventions for naming an- notation types. Test classes are named starting with the name of the class they are testing, and ending with Test. For example, HashTest or HashIntegrationTest. 5.2 JUnit test method names to separate logical compo- nents of the name. One typical pattern is test_, for example testPop_emptyStack. There is no One Correct Way to name test methods is or begins with expected. The following is a very common idiom for ensuring that the code under test does throw an exception of the expected type, so a comment is unnecessary here. try { emptyStack

Definition: Container types, like dictionaries and lists, define default iterators and membership test operators (“in” and “not in”). Pros: The default iterators and operators are simple and efficient link￿ Generally only one statement per line. However, you may put the result of a test on the same line as the test only if the entire statement fits on one line. In particular, you can never do so with

if applicable (e.g., print, plot) Unit tests should go in a separate file named originalfilename_test.R. Commenting Guidelines Comment your code. Entire commented lines should begin with # and one space

Generates random CS research papers, incl graphs and figures  Uses hand-written context-free grammar  Test for low-submission standards of conferences  Two Examples [Jeremy Stribling, Daniel Aguayo and