Good Practices
Across
- 2. Maybe the most important design decision that you make
- 5. Naming convention for constant scalar values
- 9. Prefer this over postincrement
- 10. A type of file that does not belong in a Git repository
- 11. What we should make each section of code
- 14. All functions are declared in one of this type of file
- 18. What we use in all include files to prevent double inclusion
- 20. Comment markup for status or error codes
- 21. A specifier we will not be using
- 22. Every source-code files needs exactly one of these types of comments
- 23. Do not use this in code, always use the prefix
- 26. Comment markup style with @param
- 27. The extension of files that we never include
- 28. Use this for the type when initializing a declaration with a method/function call
Down
- 1. Standard C++ integer type
- 2. Make sure each file has exactly one of these at the end of the file
- 3. Comment markup for general return
- 4. Naming convention for C-preprocessor variables
- 6. Another type of file that does not belong in a Git repository
- 7. Naming convention for C functions
- 8. All functions are defined in one of this type of file
- 9. Prefer this over postdecrement
- 12. What we want to do with temporary variables as much as possible
- 13. Use terms from this as much as possible
- 15. Kind of for statement we prefer
- 16. Naming convention for class names
- 17. The number of characters to use for indentation
- 19. Standard C++ double type
- 24. What character to use for indentation
- 25. Want to use whenever possible