Share Focus Mode

3460:421 OOP Good Practices

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