Game Development Reference
In-Depth Information
chapter 12
Microsoft Coding
All parts should go together without forcing. You must remember that the
parts you are reassembling were disassembled by you. Therefore, if you
can't get them together again, there must be a reason. By all means, do not
use a hammer.
1925 IBM Maintenance Manual
With all the fuss about how important it is to create maintainable code, a huge
issue that sparks numerous techno-religious debates is the idea that code should
follow a specific naming convention. The main problem is summed up by the
question: What naming convention should be used? There are a number of naming
conventions documented for developers, but typically the answer is left to person-
al preference. However, Microsoft is pushing the idea of “best practice” for a num-
ber of areas of .NET development, including standardized coding conventions. A
common problem with legacy Win32 API code is the variation among naming
conventions. It is not uncommon to find two components in the API that use
completely different conventions. However, Microsoft has enforced standards for
the .NET Class Framework that define how code should be named and formatted.
While you do not have to follow the proposed standard, it is recommended that
you do so for consistency and to make your code easier to read by other .NET
Search Nedrilad ::

Custom Search