Google C++ Style Guideusing header files. Self-contained Headers Header files should be self-contained (compile on their own) and end in .h. Non-header files that are meant for inclusion should end in .inc. 3 All header files parameter. In addition to the implicit conversions defined by the language, users can define their own, by adding appropriate members to the class definition of the source or destination type. An implicit everything else is a class. The struct and class keywords behave almost identically in C++. We add our own semantic meanings to each keyword, so you should use the appropriate keyword for the data-type you’re0 码力 | 83 页 | 238.71 KB | 1 年前3
02 Scientific Reading and Writing - Introduction to Scientific Writing WS2021/22Reading and Writing Matthias Boehm, Graz University of Technology, WS 2021/22 Proofreading Your Own Paper #1 Read Slowly & Carefully Problem: Brain interpolates between words Awareness of common Goals: paper selection, ensure high quality, constructive feedback and recommendations, widen own horizon Lots of similarities to code reviews in OSS Learning by What NOT to Do Accept if rejected Meaningless mix of sentences and technical terms (today: GPT-3, what’s the take-away for your own papers?) Scientific Reading 14 706.015 Introduction to Scientific Writing – 02 Scientific Reading0 码力 | 26 页 | 613.57 KB | 1 年前3
Google's R Style Guidecharacters 4. Indentation: two spaces, no tabs 5. Spacing 6. Curly Braces: first on same line, last on own line 7. else: Surround else with braces 8. Assignment: use <-, not = 9. Semicolons: don’t use them comma 3 Curly Braces An opening curly brace should never go on its own line; a closing curly brace should always go on its own line. You may omit curly braces when a block consists of a single statement;0 码力 | 8 页 | 47.42 KB | 1 年前3
03 Experiments, Reproducibility, and Projects - Introduction to Scientific Writing WS2021/22controlled and understandable scope Bottom-up approach #3 Benchmarks Evaluate on community/own benchmarks Examples: TPC-C, TPC-H, TPC-DS, JOB, MLPerf #4 End-to-end Applications Evaluate Overview Proper planning helps to keep you from “getting lost” Repeatable experiments simplify your own work There is no single way how to do it right There are many ways how to do it wrong Basic summary (7min + 3min Q&A) Timeline Oct 28: List of projects proposals, feel free to bring your own, or ask for extended proposals (e.g., ML systems, distributed systems) Nov 11: project selection0 码力 | 31 页 | 1.38 MB | 1 年前3
01 Structure of Scientific Papers - Introduction to Scientific Writing WS2021/22summary (7min + 3min Q&A) Timeline Today: List of projects proposals, feel free to bring your own Nov 11: project selection via email to m.boehm@tugraz.at (11.59pm) subject: [Scientific Writing] conferences/journals (act as filter) Make the paper useful for others (ideas, evidence, code) Example (my own theses/books) Seminar (~bachelor), 5 months, 446 pages Diploma (~master), 9 months, 274 pages0 码力 | 36 页 | 1.12 MB | 1 年前3
Google Java Style Guide4.1 Exactly one top-level class declaration Each top-level class resides in a source file of its own. 3.4.2 Class member ordering The ordering of the members of a class can have a great effect on learnability constructor appear immediately after the documentation block, and each annotation is listed on a line of its own (that is, one annotation per line). These line breaks do not constitute line- wrapping (Section 4.50 码力 | 19 页 | 84.76 KB | 1 年前3
Google Python Style Guidedeprecated string-based exceptions (raise 'Error message'). • Modules or packages should define their own domain-specific base excep- tion class, which should inherit from the built-in Exception class. The very long long ' 'long long long long long long string') Within comments, put long URLs on their own line if necessary. Yes: # See details at # https://www.example.com/us/developer/documentation/api/content/v20 码力 | 30 页 | 94.81 KB | 1 年前3
共 7 条
- 1













