C sharp (programming language)

Download 98.58 Kb.
Size98.58 Kb.

C Sharp (programming language)

C# (pronounced C Sharp) is a multi-paradigm programming language that encompasses functional, imperative, generic and object-oriented (class-based) programming disciplines. It is developed by Microsoft as part of the .NET initiative and later approved as a standard by ECMA (ECMA-334) and ISO (ISO/IEC 23270). Anders Hejlsberg, the designer of Delphi, leads development of the C# language, which has an object-oriented syntax based on C++ and includes influences from aspects of several other programming languages (most notably Delphi and Java) with a particular emphasis on simplification.

Design goals

The ECMA standard lists these design goals for C#:

  • C# is intended to be a simple, modern, general-purpose, object-oriented programming language.

  • Because software robustness, durability and programmer productivity are important, the language should include strong type checking, array bounds checking, detection of attempts to use uninitialized variables, source code portability, and automatic garbage collection.

  • The language is intended for use in developing software components that can take advantage of distributed environments.

  • Programmer portability is very important, especially for those programmers already familiar with C and C++.

  • Support for internationalization is very important.

  • C# is intended to be suitable for writing applications for both hosted and embedded systems, ranging from the very large that use sophisticated operating systems, down to the very small having dedicated functions.

  • Although C# applications are intended to be economical with regard to memory and processing power requirements, the language is not intended to compete directly on performance and size with C or assembly language.


During the development of .NET, the class libraries were originally written in a language/compiler called Simple Managed C (SMC).[2][3][4] In January 1999, Anders Hejlsberg formed a team to build a new language at the time called Cool.[5] By the time the .NET project was publicly announced at the July 2000 Professional Developers Conference (PDC), the language had been renamed C# and the class libraries and ASP.NET runtime had been ported to C#.

C#'s principal designer and lead architect at Microsoft is Anders Hejlsberg, who was previously involved with the design of Visual J++, Borland Delphi, and Turbo Pascal. In interviews and technical papers he has stated that flaws in most major programming languages (e.g. C++, Java, Delphi, and Smalltalk) drove the fundamentals of the Common Language Runtime (CLR), which, in turn, drove the design of the C# programming language itself. Some argue that C# shares roots in other languages.[6]


By design, C# is the programming language that most directly reflects the underlying Common Language Infrastructure (CLI). Most of C#'s intrinsic types correspond to value-types implemented by the CLI framework. However, the C# 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 (CLR), 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; in practice, all existing C# implementations target CIL.

C# differs from C and C++ as much as it resembles Java, including:

  • There are no global variables or functions. All methods and members must be declared within classes. It is possible, however, to use static methods/variables within public classes instead of global variables/functions.

  • Local variables cannot shadow variables of the enclosing block, unlike C and C++. Variable shadowing is often considered confusing by C++ texts.

  • C# supports a strict boolean type, bool. Statements that take conditions, such as while and if, require an expression of a boolean type. While C++ also has a boolean type, it can be freely converted to and from integers, and expressions such as if(a) require only that a is convertible to bool, allowing a 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 bool can prevent certain types of programming mistakes such as if (a = b) (use of = instead of ==).

  • 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 references, which cannot be made invalid. 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 System.IntPtr type, but cannot dereference them.

  • Managed memory cannot be explicitly freed, but is automatically garbage collected. Garbage collection addresses memory leaks. C# also provides direct support for deterministic finalization with the using statement (supporting the Resource Acquisition Is Initialization idiom).

  • 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, avoid dependency hell and simplify architectural requirements throughout CLI.

  • C# is more typesafe than C++. The only implicit conversions by default are those which are considered safe, such as widening of integers and conversion from a derived type to a base type. This is enforced at compile-time, during JIT, and, in some cases, at runtime. There are no implicit conversions between booleans and integers and between enumeration members and integers (except 0, which can be implicitly converted to an enumerated type), and any user-defined conversion must be explicitly marked as explicit or implicit, unlike C++ copy constructors (which are implicit by default) and conversion operators (which are always implicit).

  • Enumeration members are placed in their own namespace.

  • Accessors called properties can be used to modify an object with syntax that resembles C++ member field access. In C++, declaring a member public enables both reading and writing to that member, and accessor methods must be used if more fine-grained control is needed. In C#, properties allow control over member access and data validation.

  • Full type reflection and discovery is available.

  • C# currently (as of 3 June 2008) has 77 reserved words.

Common Type system (CTS)

C# has a unified type system. This unified type system is called Common Type System (CTS).

A unified type system implies that all types, including primitives such as integers, are subclasses of the System.Object class. For example, every type inherits a ToString() method. For performance reasons, primitive types (and value types in general) are internally allocated on the stack.

Categories of datatypes

CTS separates datatypes into two categories:

  • Value Type

  • Reference Type

While value types are those in which the value itself is stored by allocating memory on the stack, reference types are those in which only the address to the location where the value is present, is stored. Value types include integers (short, long), floating-point numbers (float, double), decimal (a base 10 number), structures, enumerations, booleans and characters while reference types include objects, strings, classes, interfaces and delegates.

User-defined datatypes

C# also allows the programmer to create user-defined value types, using the struct keyword. From the programmer's perspective, they can be seen as lightweight classes. Unlike regular classes, and like the standard primitives, such value types are allocated on the stack rather than on the heap. They can also be part of an object (either as a field or boxed), or stored in an array, without the memory indirection that normally exists for class types. Structs also come with a number of limitations. Because structs have no notion of a null value and can be used in arrays without initialization, they are implicitly initialized to default values (normally by filling the struct memory space with zeroes, but the programmer can specify explicit default values to override this). The programmer can define additional constructors with one or more arguments. This also means that structs lack a virtual method table, and because of that (and the fixed memory footprint), they cannot allow inheritance (but can implement interfaces).

Type casting in C#

Type casting is the process of converting a value belonging to a particular data type (or instance) to another.


using System;

class Employee { }

class ContractEmployee : Employee



class CastExample5


public static void Main ()


Employee e = new Employee();

Console.WriteLine("e = {0}",

e == null ? "null" : e.ToString());

ContractEmployee c = e as ContractEmployee;

Console.WriteLine("c = {0}",

c == null ? "null" : c.ToString());



Here, the element e, which is an instance of the class Employee, is type cast as an instance of the class ContractEmployee and stored in element c.

Certain datatypes are incompatible for type casting. For example, an integer value cannot be type-casted into a string though the converse is possible. With regard to user-defined data types, the compiler allows all kinds of type-casting. However, an InvalidCastException is thrown at runtime if the datatypes are incompatible.

Boxing and unboxing

Boxing and unboxing are two new concepts introduced in C#.

Boxing is the method used to convert a value type into a reference type.


int foo = 42; // Value type...

object bar = foo; // foo is boxed to bar.

Unboxing is the method used to convert a reference type into a value type.


int foo = 42; // Value type.

object bar = foo; // foo is boxed to bar.

int foo2 = (int)bar; // Unboxed back to value type.

Boxing and unboxing become important when value types are put into a collection class or taken out of a collection class.

Features of C# 2.0

New features in C# for the .NET SDK 2.0 (corresponding to the 3rd edition of the ECMA-334 standard) are:

Partial class

Partial classes allow class implementation across more than one source file. This permits splitting up very large classes, and is also useful if some parts of a class are automatically generated.


public partial class MyClass


public void MyMethod1()


// implementation




public partial class MyClass


public void MyMethod2()


// implementation




Generics, or parameterized types, is a .NET 2.0 feature supported by C#. Unlike C++ templates, .NET parameterized types are instantiated at runtime rather than by the compiler; hence they can be cross-language whereas C++ templates cannot. They support some features not supported directly by C++ templates such as type constraints on generic parameters by use of interfaces. On the other hand, C# does not support non-type generic parameters. Unlike generics in Java, .NET generics use reification to make parameterized types first-class objects in the CLI Virtual Machine, which allows for optimizations and preservation of the type information.[7]

Static classes that cannot be instantiated

Static classes that cannot be instantiated, and that only allow static members. This is similar to the concept of module in many procedural languages.

A new form of iterator providing generator functionality

A new form of iterator that provides generator functionality, using a yield return construct similar to yield in Python.

// Method that takes an iterable input (possibly an array) and returns all even numbers.

public static IEnumerable GetEven(IEnumerable numbers)


foreach (int i in numbers)


if (i % 2 == 0) yield return i;



Anonymous delegates

Anonymous delegates providing closure-like functionality.[8]

public void Foo(object parameter) {

// ...



// anonymous delegates have full access to local variables of the enclosing method

if (parameter == ...)


// ...


// ...



Covariance and contravariance for signatures of delegates

Covariance and contravariance for signatures of delegates[9]

The accessibility of property accessors can be set independently


string status = string.Empty;

public string Status


get { return status; } // anyone can get value of this property,

protected set { status = value; } // but only derived classes can change it


Nullable types

Nullable value types (denoted by a question mark, e.g. int? i = null;) which add null to the set of allowed values for any value type. This provides improved interaction with SQL databases, which can have nullable columns of types corresponding to C# primitive types: an SQL INTEGER NULL column type directly translates to the C# int?.

Nullable types received an eleventh-hour improvement at the end of August 2005, mere weeks before the official launch, to improve their boxing characteristics: a nullable variable which is assigned null is not actually a null reference, but rather an instance of struct Nullable with property HasValue equal to false. When boxed, the Nullable instance itself is boxed, and not the value stored in it, so the resulting reference would always be non-null, even for null values. The following code illustrates the corrected flaw:

int? i = null;

object o = i;

if (o == null)

Console.WriteLine("Correct behaviour - runtime version from September 2005 or later");


Console.WriteLine("Incorrect behaviour - pre-release runtime (from before September 2005)");

When copied into objects, the official release boxes values from Nullable instances, so null values and null references are considered equal. The late nature of this fix caused some controversy[citation needed], since it required core-CLR changes affecting not only .NET2, but all dependent technologies (including C#, VB, SQL Server 2005 and Visual Studio 2005).

Coalesce operator

(??) returns the first of its operands which is not null (or null, if no such operand exists):

object nullObj = null;

object obj = new Object();

return nullObj ?? obj; // returns obj

The primary use of this operator is to assign a nullable type to a non-nullable type with an easy syntax:

int? i = null;

int j = i ?? 0; // Unless i is null, initialize j to i. Else (if i is null), initialize j to 0.

Features of C# 3.0

C# 3.0 is the current version, and was released on 19 November 2007 as part of .NET Framework 3.5. It includes new features inspired by functional programming languages such as Haskell and ML, and is driven largely by the introduction of the Language Integrated Query (LINQ) pattern to the Common Language Runtime.[10]


Language Integrated Query:[11] "from, where, select" context-sensitive keywords allowing queries across SQL, XML, collections, and more. These are treated as keywords in the LINQ context, but their addition won't break existing variables named from, where, or select.

Object initializers

Customer c = new Customer(); c.Name = "James";

can be written

Customer c = new Customer { Name="James" };

Collection initializers

MyList list = new MyList(); list.Add(1); list.Add(2); can be written as MyList list = new MyList { 1, 2 }; (assuming that MyList implements System.Collections.IEnumerable and has a public Add method[12])

Anonymous types

var x = new { Name = "James" }

Local variable type inference

Local variable type inference: var x = "hello"; is interchangeable with string x = "hello";. More than just syntactic sugar, this feature is required for the declaration of anonymous typed variables.

Lambda expressions

Lambda expressions: listOfFoo.Where(delegate(Foo x) { return x.Size > 10; }) can be written listOfFoo.Where(x => x.Size > 10);

Compiler-inferred translation of Lambda expressions to either strongly-typed function delegates or strongly-typed expression trees.

Automatic properties

The compiler will automatically generate a private instance variable and the appropriate getter and setter given code such as: public string Name { get; private set; }

Extension methods

Extension methods (adding methods to classes by including the this keyword in the first parameter of a method on another static class):

public static class IntExtensions


public static void PrintPlusOne(this int x) { Console.WriteLine(x + 1); }


int foo = 0;


Partial methods

Allow codegenerators to generate method declarations as extension points that are only included in the source code compilation if someone actually implements it in another portion of a partial class.[13]

C# 3.0 was unveiled at the 2005 Professional Developers Conference.[14] It is not currently standardized by any standards organisation, though it is expected that it will eventually become an ECMA and then ISO standard, as did its predecessors.

Microsoft has emphasized that the new language features of C# 3.0 will be available without any changes to the runtime. This means that C# 2.0 and 3.0 will be binary-compatible (CLI implementations compatible with 2.0 are able to run 3.0 applications directly).

Although the new features may only slightly change simple in-memory queries, such as List.FindAll or List.RemoveAll, the pattern used by LINQ allows for significant extension points to enable queries over different forms of data, both local and remote.


C# features "preprocessor directives"[15] (though it does not have an actual preprocessor) based on the C preprocessor that allow programmers to define symbols but not macros. Conditionals such as #if, #endif, and #else are also provided. Directives such as #region give hints to editors for code folding.

Code comments

C# utilizes a double forward slash (//) to indicate the rest of the line is a comment. Comments can also be indicated using a starting forward slash/asterisk (/*) and ending asterisk/forward slash (*/).

public class Foo


// a comment

public static void Bar(int firstParam) {} //Also a comment


public class FooBar


/* a comment */

public static void BarFoo(int firstParam) {} /* Also a comment */


Multi-line comments can also be indicated by a starting forward slash/asterisk (/*) and ending asterisk/forward slash (*/).

public class Foo


/* A Multi-Line

comment */

public static void Bar(int firstParam) {}


XML documentation system

C#'s documentation system is similar to Java's Javadoc, but based on XML. Two methods of documentation are currently supported by the C# compiler.

Single-line comments, such as those commonly found in Visual Studio generated code, are indicated on a line beginning with ///.

public class Foo



A summary of the method.

A description of the parameter.

/// Remarks about the method.

public static void Bar(int firstParam) {}


Multi-line comments, while defined in the version 1.0 language specification, were not supported until the .NET 1.1 release.[16] These comments are designated by a starting forward slash/asterisk/asterisk (/**) and ending asterisk/forward slash (*/)[17].

public class Foo



A summary of the method.

A description of the parameter.

* Remarks about the method. */

public static void Bar(int firstParam) {}


Note there is some stringent criteria regarding white space and XML documentation when using the forward slash/asterisk/asterisk (/**) technique.

This code block:



* A summary of the method.

produces a different XML comment than this code block[17]:



A summary of the method.

Syntax for documentation comments and their XML markup is defined in a non-normative annex of the ECMA C# standard. The same standard also defines rules for processing of such comments, and their transformation to a plain XML document with precise rules for mapping of CLI identifiers to their related documentation elements. This allows any C# IDE or other development tool to find documentation for any symbol in the code in a certain well-defined way.

Future development

Future versions of C# are under development, though their exact specification is not finalized. It will feature enhanced support for Reflection as well as an enhanced Microsoft Office interop library. It will also integrate with the Dynamic Language Runtime and allow C# to call into code written in DLR-based languages (such as IronPython and IronRuby) using a syntax similar to what C# uses for CLR methods and objects. The dynamic keyword is being considered to demarcate a block where dynamic lookup will be available.[18]


The C# specification details a minimum set of types and class libraries that the compiler expects to have available and they define the basics required. In practice, C# is most often used with some implementation of the Common Language Infrastructure (CLI), which is standardized as ECMA-335 Common Language Infrastructure (CLI).

Hello world example

The following is a very simple C# program, a version of the classic "Hello world" example:

class ExampleClass


static void Main()


System.Console.WriteLine("Hello, world!");



The effect is to write the following text to the output console:

Hello, world!

Each line has a purpose:

class ExampleClass

Above is a class definition. Everything between the following pair of braces describes ExampleClass.

static void Main()

This declares the class member method where the program begins execution. The .NET runtime calls the Main method. (Note: Main may also be called from elsewhere, e.g. from the code Main() in another method of ExampleClass.) The static keyword makes the method accessible without an instance of ExampleClass. Each console application's Main entry point must be declared static. Otherwise, the program would require an instance, but any instance would require a program. To avoid that irresolvable circular dependency, C# compilers processing console applications (like above) report an error if there is no static Main method. The void keyword declares that Main has no return value (see also side effect).

Console.WriteLine("Hello, world!");

This line writes the output. Console is a static class in the System namespace. It provides an interface to the standard input, output, and error streams for console applications. The program calls the Console method WriteLine, which displays on the console a line with the argument, the string "Hello, world!".


In August, 2000, Microsoft Corporation, Hewlett-Packard and Intel Corporation co-sponsored the submission of specifications for C# as well as the Common Language Infrastructure (CLI) to the standards organization ECMA International. In December 2001 , ECMA released ECMA-334 C# Language Specification. C# became an ISO standard in 2003 (ISO/IEC 23270:2006 - Information technology -- Programming languages -- C#). ECMA had previously adopted equivalent specifications as the 2nd edition of C#, in December, 2002.

In June 2005, ECMA approved edition 3 of the C# specification, and updated ECMA-334. Additions included partial classes, anonymous methods, nullable types, and generics (similar to C++ templates).

In July 2005, ECMA submitted the standards and related TRs to ISO/IEC JTC 1 via the latter's Fast-Track process. This process usually takes 6-9 months.



All programs written for .NET and other similar virtual machine environments tend to require much more memory than functionally similar applications written in languages like C++, which do not have an extensive associated library[19]. C# CPU speed is also lower than for native languages[20][21]


Microsoft's current .NET implementation is only available on Windows, though this relates more to the availability of some non-standard libraries developed by Microsoft, rather than the C# language itself. There are other environments that support C# programs on Windows, Linux, BSD or Mac OS X, and while some provide a complete implementation of the C# language and CLI, none provide a complete implementation of every library available from Microsoft. See Mono[22] and DotGNU[23] In November 2002 Microsoft released a 1.0 CLI implementation that worked on Free BSD and Mac OS X 10.2, but the next versions were only made available on Windows.


Although the C# language definition and the CLI are standardized under ISO and ECMA standards, the CLI is only a part of Microsoft's Base Class Library (BCL), which also contains non-standardized classes that are used by many C# programs (some extended IO, User Interface, Web services, ...). Furthermore, parts of the BCL have been patented by Microsoft,[24][25] which may deter independent implementations of the full framework, as only the standardized portions have RAND protection from patent claims.


The de facto standard implementation of the C# language is Microsoft's C# compiler, Visual C#.

Alternative C# compilers are:

  • Microsoft's Rotor project (currently called Shared Source Common Language Infrastructure) (licensed for educational and research use only) provides a shared source implementation of the CLR runtime and a C# compiler, and a subset of the required Common Language Infrastructure framework libraries in the ECMA specification.

  • The Mono project provides an open source C# compiler, a complete open source implementation of the Common Language Infrastructure including the required framework libraries as they appear in the ECMA specification, and a nearly complete[citation needed] implementation of the remaining Microsoft proprietary .NET class libraries (libraries not documented or included in the ECMA specification but included in Microsoft's standard .NET Framework distribution).

  • The DotGNU project also provides an open source C# compiler, a nearly complete implementation of the Common Language Infrastructure including the required framework libraries as they appear in the ECMA specification, and subset of some of the remaining Microsoft proprietary .NET class libraries (those not documented or included in the ECMA specification but included in Microsoft's standard .NET Framework distribution).

Language name

C sharp typographical convention

C sharp musical note

The name "C sharp" was inspired from musical notation where a sharp indicates that the written note should be made a half-step higher in pitch.[26] This is similar to the language name of C++, where the ++ symbol indicates that a variable should be incremented by 1.

Due to technical limitations of display (fonts, browsers, etc.) and the fact that the sharp symbol (, U+266F, MUSIC SHARP SIGN) is not present on the standard keyboard, the Number sign (#, U+0023, NUMBER SIGN) was chosen to represent the sharp symbol in the written name of the programming language.[27] This convention is reflected in the ECMA-334 C# Language Specification.[28] However, when it is practical to do so (for example, in advertising or in box art[29]), Microsoft will use the intended musical sharp symbol.

The "sharp" suffix has been used by a number of other .NET languages that are variants of existing languages, including J# (Microsoft's implementation of Java), A# (from Ada), and F# (presumably from System F, the type system used by the ML family).[30] The original implementation of Eiffel for .NET was called Eiffel#, a name since retired since the full Eiffel language is now supported. The suffix is also sometimes used for libraries, such as Gtk# (a .NET wrapper for GTK+ and other GNOME libraries), Cocoa# (a wrapper for Cocoa) and Qt# (a .NET language binding for the Qt toolkit).

Environments and tools

  • Microsoft Visual Studio, IDE for C#

  • SharpDevelop, an open-source C# IDE for Windows

  • MonoDevelop, an open-source C# IDE for Linux

  • QuickSharp 2008, a simplified development environment for C#

  • Morfik C#, a C# to JavaScript compiler complete with IDE and framework for Web application development.

  • Baltie, an educational IDE for children and students with little or no programming experience

  • Borland Turbo C Sharp

Download 98.58 Kb.

Share with your friends:

The database is protected by copyright ©ininet.org 2020
send message

    Main page