Book Image

Clean Code in C#

By : Jason Alls
Book Image

Clean Code in C#

By: Jason Alls

Overview of this book

Traditionally associated with developing Windows desktop applications and games, C# is now used in a wide variety of domains, such as web and cloud apps, and has become increasingly popular for mobile development. Despite its extensive coding features, professionals experience problems related to efficiency, scalability, and maintainability because of bad code. Clean Code in C# will help you identify these problems and solve them using coding best practices. The book starts with a comparison of good and bad code, helping you understand the importance of coding standards, principles, and methodologies. You’ll then get to grips with code reviews and their role in improving your code while ensuring that you adhere to industry-recognized coding standards. This C# book covers unit testing, delves into test-driven development, and addresses cross-cutting concerns. You’ll explore good programming practices for objects, data structures, exception handling, and other aspects of writing C# computer programs. Once you’ve studied API design and discovered tools for improving code quality, you’ll look at examples of bad code and understand which coding practices you should avoid. By the end of this clean code book, you’ll have the developed skills you need in order to apply industry-approved coding practices to write clean, readable, extendable, and maintainable C# code.
Table of Contents (17 chapters)

Checked and unchecked exceptions

In unchecked mode, an arithmetic overflow is ignored. In this situation, the high-order bits that cannot be assigned to the destination type are discarded from the result.

By default, C# operates in the unchecked context while performing non-constant expressions at runtime. But compile-time constant expressions are always checked by default. When an arithmetic overflow is encountered in checked mode, an OverflowException is raised. One reason why unchecked exceptions are used is to increase performance. Checked exceptions can decrease the performance of methods by a small amount.

The rule of thumb is to make sure that you perform arithmetic operations in the checked context. Any arithmetic overflow exceptions will be picked up as compile-time errors, and you can then fix them before you release your code. That is much better than releasing your code and then having to fix customer runtime errors.

Running code in unchecked...