ស៊ីទ្រុងជ្រូក: Distinguishing features

Distinguishing features 
Note: The following description is based on the language standard and other documents listed in the "External links" section.

By design, C# is the programming language that most directly reflects the underlying Common Language Infrastructure (CLI). Most of its intrinsic types correspond to value-types implemented by the CLI framework. However, the language specification does not state the code generation requirements of the compiler: that is, it does not state that a C# compiler must target a Common Language Runtime, or generate Common Intermediate Language (CIL), or generate any other specific format. Theoretically, a C# compiler could generate machine code like traditional compilers of C++ or Fortran.

Some notable features of C# that distinguish it from C and C++ (and Java, where noted) are:

 វាមិនមានអថេរ ឬមុខងារសកលទេ។ All methods and members must be declared within classes. Static members of public classes can substitute for global variables and functions.
 Local variables cannot shadow variables of the enclosing block, unlike C and C++.

 C# supports a strict Boolean data type, . Statements that take conditions, such as  and , require an expression of a type that implements the  operator, such as the boolean type. While C++ also has a boolean type, it can be freely converted to and from integers, and expressions such as  require only that  is convertible to bool, allowing  to be an int, or a pointer. C# disallows this "integer meaning true or false" approach, on the grounds that forcing programmers to use expressions that return exactly  can prevent certain types of common programming mistakes in C or C++ such as  (a = b) (use of assignment = instead of equality ==).
 In C#, memory address pointers can only be used within blocks specifically marked as unsafe, and programs with unsafe code need appropriate permissions to run. Most object access is done through safe object references, which always either point to a "live" object or have the well-defined null value; it is impossible to obtain a reference to a "dead" object (one that has been garbage collected), or to a random block of memory. An unsafe pointer can point to an instance of a value-type, array, string, or a block of memory allocated on a stack. Code that is not marked as unsafe can still store and manipulate pointers through the  type, but it cannot dereference them.
 Managed memory cannot be explicitly freed; instead, it is automatically garbage collected. Garbage collection addresses the problem of memory leaks by freeing the programmer of responsibility for releasing memory that is no longer needed.
 In addition to the  construct to handle exceptions, C# has a  construct to guarantee execution of the code in the  block, whether an exception occurs or not.
 Multiple inheritance is not supported, although a class can implement any number of interfaces. This was a design decision by the language's lead architect to avoid complication and simplify architectural requirements throughout CLI.
 C#, like C++, but unlike Java, supports operator overloading.

 C# is more type safe than C++. The only implicit conversions by default are those that are considered safe, such as widening of integers. This is enforced at compile-time, during JIT, and, in some cases, at runtime. No implicit conversions occur between booleans and integers, nor between enumeration members and integers (except for literal 0, which can be implicitly converted to any enumerated type). Any user-defined conversion must be explicitly marked as explicit or implicit, unlike C++ copy constructors and conversion operators, which are both implicit by default. Starting with version 4.0, C# supports a "dynamic" data type that enforces type checking at runtime only.
 Enumeration members are placed in their own scope.
 C# provides properties as syntactic sugar for a common pattern in which a pair of methods, accessor (getter) and mutator (setter) encapsulate operations on a single attribute of a class. No redundant method signatures for the getter/setter implementations need be written, and the property may be accessed using attribute syntax rather than more verbose method calls.
 Checked exceptions are not present in C# (in contrast to Java). This has been a conscious decision based on the issues of scalability and versionability.
 Though primarily an imperative language, since C# 3.0 it supports functional programming techniques through first-class function objects and lambda expressions.