code base. If a feature in the C++ standard solves a problem, or if some idiom is widely known and accepted, that’s an argument for using it. However, sometimes standard features and idioms are flawed, or below) it’s appropriate to constrain or ban standard features. In some cases we prefer a homegrown or third-party library over a library defined in the C++ Standard, either out of perceived superiority or or insufficient value to transition the codebase to the standard interface. Avoid surprising or dangerous constructs C++ has features that are more surprising or dangerous than one might think at a glance

error codes. Cons: May cause the control flow to be confusing. Easy to miss error cases when making library calls. 4 Decision: Exceptions must follow certain conditions: • Raise exceptions like this: raise setter methods. Definition: A way to wrap method calls for getting and setting an attribute as a standard attribute access when the computation is lightweight. Pros: Readability is increased by eliminating blank lines as you judge appropriate within 18 functions or methods. Whitespace link￿ Follow standard typographic rules for the use of spaces around punctuation. No whitespace inside parentheses, brackets

com/meet/m.boehm  Optional attendance (independent of COVID)  #2 Course Registrations (as of Oct 29)  Changes in WS20/21, now max constraints  Introduction to Scientific Writing ISDS Group Boehm 39/40 3 Technology, WS 2021/22 Page Limits  Most Conferences/Journals  Given predefined template, changes not permitted  SIGMOD/PVDLB: 12 pages + unlimited references  ICDE: 12 pages incl. references

com/meet/m.boehm  Optional attendance (independent of COVID)  #2 Course Registrations (as of Nov 05)  Changes in WS20/21, now max constraints  Introduction to Scientific Writing  #3 Timeline  Nov 11: project

com/meet/m.boehm  Optional attendance (independent of COVID)  #2 Course Registrations (as of Oct 28)  Changes in WS20/21, now max constraints  Introduction to Scientific Writing ISDS Group Boehm 40/40 3

File description comment, including purpose of program, inputs, and out- puts 4. source() and library() statements 5. Function definitions 6. Executed statements, if applicable (e.g., print, plot) Unit num.days, show.plot = TRUE) Ideally, unit tests should serve as sample function calls (for shared library rou- tines). Function Documentation Functions should contain a comments section immediately below

first has

immediately before the first word, with no space after. 7.1.3 At-clauses Any of the standard “at-clauses” that are used appear in the order @param, @return, @throws, @deprecated, and these