Software Coding Standards - Additional Remarks
2010 29 Mar
Let’s face it; we all d/o bad things while coding one time or another. Let’s avoid them as best as we can because we may read the code one year later, and we'll not be able to easiely understand it. In addition to the points that we handeled in the series of software coding standards, let’s pass by some points, which enhance our coding skills:
- Avoid putting using statements inside a namespace
- Check spelling in comments
- Always start left curly brace { on a new line Group framework namespaces together; add custom and thirdparty namespaces below Use strict indentation (3 or 4 spaces, no tabs)
- Avoid fully qualified type names
- Indent comment at the same line as the code
- All member variables should be declared at the top of classes; properties and methods should be separated by one line each
- Declare local variables as close as possible to the first time they’re used
- File names should reflect the classes that they contain
Thank you for reading my coding standards topics and I hope that I did explain and light on the common coding mistakes.
Comments