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