C Sharp (programming language)

From Seo Wiki - Search Engine Optimization and Programming Languages

Jump to: navigation, search


C# (pronounced "see sharp") is a multi-paradigm programming language encompassing imperative, functional, generic, object-oriented (class-based), and component-oriented programming disciplines. It was developed by Microsoft within the .NET initiative and later approved as a standard by Ecma (ECMA-334) and ISO (ISO/IEC 23270). C# is one of the programming languages designed for the Common Language Infrastructure.

C# is intended to be a simple, modern, general-purpose, object-oriented programming language.[1] Its development team is led by Anders Hejlsberg, the designer of Borland's Turbo Pascal, who has said that its object-oriented syntax is based on C++ and other languages.[2] The most recent version is C# 3.0, which was released in conjunction with the .NET Framework 3.5 in 2007. The next proposed version, 4.0, is in development.


Design goals

The Ecma standard lists these design goals for C#:[1]

  • C# language is intended to be a simple, modern, general-purpose, object-oriented programming language.
  • The language, and implementations thereof, should provide support for software engineering principles such as strong type checking, array bounds checking, detection of attempts to use uninitialized variables, and automatic garbage collection. Software robustness, durability, and programmer productivity are important.
  • The language is intended for use in developing software components suitable for deployment in distributed environments.
  • Source code portability is very important, as is programmer portability, 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 was not intended to compete directly on performance and size with C or assembly language.

Language name

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.[3] This is similar to the language name of C++, where "++" indicates that a variable should be incremented by 1.

Due to technical limitations of display (standard fonts, browsers, etc.) and the fact that the sharp symbol ([[Sharp (music)|Template:Music]], 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.[4] This convention is reflected in the ECMA-334 C# Language Specification.[1] However, when it is practical to do so (for example, in advertising or in box art[5]), Microsoft uses the intended musical symbol.

The "sharp" suffix has been used by a number of other .NET languages that are variants of existing languages, including J# (a .NET language also designed by Microsoft which is derived from Java 1.1), A# (from Ada), and the functional F#.[6] The original implementation of Eiffel for .NET was called Eiffel#,[7] a name since retired since the full Eiffel language is now supported. The suffix has also been 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).


During the development of the .NET Framework, the class libraries were originally written using a managed code compiler system called Simple Managed C (SMC).[8][9][10] In January 1999, Anders Hejlsberg formed a team to build a new language at the time called Cool, which stood for "C-like Object Oriented Language".[11] Microsoft had considered keeping the name "Cool" as the final name of the language, but chose not to do so for trademark reasons. By the time the .NET project was publicly announced at the July 2000 Professional Developers Conference, 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 Turbo Pascal, Embarcadero Delphi (formerly CodeGear Delphi and Borland Delphi), and Visual J++. 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.

James Gosling, who created the Java programming language in 1994, and Billy Joy, a co-founder of Sun Microsystems, the proprietor of Java, called C# an "imitation" of Java; Gosling further claimed that "[C# is] sort of Java with reliability, productivity and security deleted."[12][13] Klaus Kreft and Angelika Langer (authors of a C++ streams book) stated in a blog post that "Java and C# are almost identical programming languages. Boring repetition that lacks innovation," "Hardly anybody will claim that Java or C# are revolutionary programming languages that changed the way we write programs," and "C# borrowed a lot from Java - and vice versa. Now that C# supports boxing and unboxing, we'll have a very similar feature in Java." [14]


In the course of its development, the C# language has gone through several versions:

Version Language Specification Microsoft Compiler
C# 1.0 December 2001 January 2002
C# 2.0 December 2002 November 2005
C# 3.0 June 2005 November 2006
C# 4.0 June 2006 Intended release March 2010 [15] (Expected delayed)


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 distinguishing features of C# are:

  • There are no global variables or functions. 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++. Variable shadowing is often considered confusing by C++ texts.
  • C# supports a strict Boolean datatype, bool. Statements that take conditions, such as while and if, require an expression of a type that implements the true 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 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 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 which 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 System.IntPtr 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 which is no longer needed.
  • In addition to the try...catch construct to handle exceptions, C# has a try...finally construct to guarantee execution of the code in the finally block.
  • 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# is more typesafe than C++. The only implicit conversions by default are those which are considered safe, such as widening of integers. This is enforced at compile-time, during JIT, and, in some cases, at runtime. There are no implicit conversions 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.
  • 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.
  • 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).[16]

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[16]:

  1. Value types
  2. Reference types

Value types are plain aggregations of data. Instances of value types do not have referential identity nor a referential comparison semantics - equality and inequality comparisons for value types compare the actual data values within the instances, unless the corresponding operators are overloaded. Value types are derived from System.ValueType, always have a default value, and can always be created and copied. Some other limitations on value types are that they cannot derive from each other (but can implement interfaces) and cannot have an explicit default (parameterless) constructor. Examples of value types are some primitive types, such as int (a signed 32-bit integer), float (a 32-bit IEEE floating-point number), char (a 16-bit Unicode code unit), and System.DateTime (identifies a specific point in time with nanosecond precision). Other examples are enum (enumerations) and struct(user defined structures).

In contrast, reference types have the notion of referential identity - each instance of a reference type is inherently distinct from every other instance, even if the data within both instances is the same. This is reflected in default equality and inequality comparisons for reference types, which test for referential rather than structural equality, unless the corresponding operators are overloaded (such as the case for System.String). In general, it is not always possible to create an instance of a reference type, nor to copy an existing instance, or perform a value comparison on two existing instances, though specific reference types can provide such services by exposing a public constructor or implementing a corresponding interface (such as ICloneable or IComparable). Examples of reference types are object (the ultimate base class for all other C# classes), System.String (a string of Unicode characters), and System.Array (a base class for all C# arrays).

Both type categories are extensible with user-defined types.

Boxing and unboxing

Boxing is the operation of converting a value of a value type into a value of a corresponding reference type.[16] Boxing in C# is implicit.

Unboxing is the operation of converting a value of a reference type (previously boxed) into a value of a value type.[16] Unboxing in C# requires an explicit type cast.


int foo = 42;         // Value type.
object bar = foo;     // foo is boxed to bar.
int foo2 = (int)bar;  // Unboxed back to value type.


C# features "preprocessor directives"[17] (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.

public class Foo
    #region Procedures
    public void IntBar(int firstParam) {}  
    public void StrBar(string firstParam) {}  
    public void BoolBar(bool firstParam) {}  
    #region Constructors
    public Foo() {}
    public Foo(int firstParam) {}

Code comments

C# utilizes a double forward slash (//<code>) to indicate the rest of the line is a comment.

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

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

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 documentation comments, such as those commonly found in Visual Studio generated code, are indicated on a line beginning with <code>///<code>.

public class Foo
    /// <summary>A summary of the method.</summary>
    /// <param name="firstParam">A description of the parameter.</param>
    /// <remarks>Remarks about the method.</remarks>
    public static void Bar(int firstParam) {}

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

public class Foo
    /** <summary>A summary of the method.</summary>
     *  <param name="firstParam">A description of the parameter.</param>
     *  <remarks>Remarks about the method.</remarks> */
    public static void Bar(int firstParam) {}

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

This code block:

 * <summary>
 * A summary of the method.</summary>*/

produces a different XML comment from this code block:[19]

 * <summary>
   A summary of the method.</summary>*/

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.


The C# specification details a minimum set of types and class libraries that the compiler expects to have available. 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:

using System;
class ExampleClass
    static void Main()
        Console.WriteLine("Hello, world!");

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

Hello, world!

Each line has a purpose:

using System;

The above line of code tells the compiler to use 'System' as a candidate prefix for types used in the source code. In this case, when the compiler sees use of the 'Console' type later in the source code, it tries to find a type named 'Console', first in the current assembly, followed by all referenced assemblies. In this case the compiler fails to find such a type, since the name of the type is actually 'System.Console'. The compiler then attempts to find a type named 'System.Console' by using the 'System' prefix from the using statement, and this time it succeeds. The using statement allows the programmer to state all candidate prefixes to use during compilation instead of always using full type names.

class ExampleClass

Above is a class definition. Everything between the following pair of braces describes <code>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.


Although the C# language definition and the CLI are standardized under ISO and Ecma standards which provide reasonable and non-discriminatory licensing protection from patent claims, Microsoft uses C# and the CLI in its Base Class Library (BCL) which is the foundation of its proprietary .NET framework, and which provides a variety of non-standardized classes (extended I/O, GUI, web services, etc). Some cases where Microsoft patents apply to standards used in the .NET framework are documented by Microsoft and the applicable patents are available on either RAND terms or through Microsoft's Open Specification Promise which releases patent rights to the public,[20] but there is some concern and debate as to whether there are additional aspects patented by Microsoft which are not covered, which may deter independent implementations of the full framework. Microsoft has also agreed not to sue open source developers for violating patents in non-profit projects for the part of the framework which is covered by the OSP.[21] Microsoft has agreed not to enforce patents relating to Novell products against Novell's paying customers[22] with the exception of a list of products that do not explicitly mention C#, .NET or Novell's implementation of .NET (The Mono Project),[23]. However Novell maintains that Mono does not infringe any Microsoft patents.[24] Microsoft has also made a specific agreement not to enforce patent rights related to the Moonlight browser plugin, which depends on Mono, provided it is obtained through Novell.[25]

In a note posted on the Free Software Foundation's news website in June 2009, Richard Stallman warned that he believes "Microsoft is probably planning to force all free C# implementations underground some day using software patents" and recommended that developers avoid taking what he described as the "gratuitous risk" associated with "depend[ing] on the free C# implementations".[26]. The Free Software Foundation later reiterated its warnings[27], claiming that the extension of Microsoft Community Promise to the C# and the CLI ECMA specifications[28] would not prevent Microsoft from harming Open-Source implementations of C#, because many specific Windows libraries included with .NET or Mono were not covered by this promise.


The reference C# compiler is Microsoft Visual C#.

Other C# compilers exist, often including an implementation of the Common Language Infrastructure and the .NET class libraries up to .NET 2.0:

  • 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 (up to C# 2.0, and supported on Windows XP only).
  • 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 implementation of the Microsoft proprietary .NET class libraries up to .NET 2.0, but not specific .NET 3.0 and .NET 3.5 libraries, as of Mono 2.0.
  • 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 up to .NET 2.0 (those not documented or included in the ECMA specification but included in Microsoft's standard .NET Framework distribution).
  • The DotNetAnywhere Micro Framework-like Common Language Runtime is targeted at embedded systems, and supports almost all C# 2.0 specifications.

See also


  1. 1.0 1.1 1.2 C# Language Specification (4th ed.). Ecma International. June 2006. http://www.ecma-international.org/publications/files/ECMA-ST/Ecma-334.pdf. Retrieved June 18, 2009. 
  2. John Osborn (2000). "Deep Inside C#: An Interview with Microsoft Chief Architect Anders Hejlsberg". O'Reilly Media. http://windowsdevcenter.com/pub/a/oreilly/windows/news/hejlsberg_0800.html. Retrieved 2009-11-14. 
  3. Kovacs, James (September 7, 2007). "C#/.NET History Lesson". http://www.jameskovacs.com/blog/CNETHistoryLesson.aspx. Retrieved June 18, 2009. 
  4. "Microsoft C# FAQ". Microsoft. http://msdn.microsoft.com/vcsharp/previous/2002/FAQ/default.aspx. Retrieved 2008-03-25. [dead link]
  5. "Visual C#.net Standard" (JPEG). Microsoft. September 4, 2003. http://www.microsoft.com/presspass/images/gallery/boxshots/web/visual-c-sharp03.jpg. Retrieved June 18, 2009. 
  6. "F# FAQ". Microsoft Research. http://research.microsoft.com/en-us/um/cambridge/projects/fsharp/faq.aspx. Retrieved June 18, 2009. 
  7. Simon, Raphael; Stapf, Emmanuel; Meyer, Bertrand (June 2002). "Full Eiffel on the .NET Framework". Microsoft. http://msdn.microsoft.com/en-us/library/ms973898.aspx. Retrieved June 18, 2009. 
  8. Zander, Jason (November 23, 2007). "Couple of Historical Facts". http://blogs.msdn.com/jasonz/archive/2007/11/23/couple-of-historical-facts.aspx. Retrieved 2008-02-21. 
  9. "C# 3.0 New Features". http://www.learnitonweb.com/Articles/ReadArticle.aspx?contId=4&page=1. Retrieved 2008-06-08. 
  10. Guthrie, Scott (November 28, 2006). "What language was ASP.Net originally written in?". http://aspadvice.com/blogs/rbirkby/archive/2006/11/28/What-language-was-ASP.Net-originally-written-in_3F00_.aspx. Retrieved 2008-02-21. 
  11. Hamilton, Naomi (October 1, 2008). "The A-Z of Programming Languages: C#". Computerworld. http://www.computerworld.com.au/article/261958/-z_programming_languages_c. Retrieved 2008-10-01. 
  12. Wylie Wong (2002). "Why Microsoft's C# isn't". CNET: CBS Interactive. http://news.cnet.com/2008-1082-817522.html. Retrieved 2009-11-14. 
  13. Bill Joy (2002-02-07). "Microsoft's blind spot". cnet.com. http://news.cnet.com/2010-1071-831385.html. Retrieved 2010-01-12. 
  14. Klaus Kreft and Angelika Langer (2003-07-03). "After Java and C# - what is next?". artima.com. http://www.artima.com/weblogs/viewpost.jsp?thread=6543. Retrieved 2010-01-12. 
  15. http://www.theregister.co.uk/2009/10/19/visual_studio_2010_second_beta_packaging/
  16. 16.0 16.1 16.2 16.3 Archer, Part 2, Chapter 4:The Type System
  17. "C# Preprocessor Directives". C# Language Reference. Microsoft. http://msdn.microsoft.com/en-us/library/ed8yd1ha.aspx. Retrieved June 18, 2009. 
  18. Horton, Anson (2006-09-11). "C# XML documentation comments FAQ". http://blogs.msdn.com/ansonh/archive/2006/09/11/750056.aspx. Retrieved 2007-12-11. 
  19. 19.0 19.1 "Delimiters for Documentation Tags". C# Programmer's Reference. Microsoft. January 1, 1970 GMT. http://msdn.microsoft.com/en-us/library/5fz4y783(VS.71).aspx. Retrieved June 18, 2009. 
  20. "Interoperability Principles". http://www.microsoft.com/interop/principles/default.mspx. 
  21. "Patent Pledge for Open Source Developers". http://www.microsoft.com/interop/principles/osspatentpledge.mspx. 
  22. "Patent Cooperation Agreement - Microsoft & Novell Interoperability Collaboration". Microsoft. November 2, 2006. http://www.microsoft.com/interop/msnovellcollab/patent_agreement.mspx. Retrieved July 5, 2009. "Microsoft, on behalf of itself and its Subsidiaries (collectively “Microsoft”), hereby covenants not to sue Novell’s Customers and Novell’s Subsidiaries’ Customers for infringement under Covered Patents of Microsoft on account of such a Customer’s use of specific copies of a Covered Product as distributed by Novell or its Subsidiaries (collectively “Novell”) for which Novell has received Revenue (directly or indirectly) for such specific copies; provided the foregoing covenant is limited to use by such Customer (i) of such specific copies that are authorized by Novell in consideration for such Revenue, and (ii) within the scope authorized by Novell in consideration for such Revenue." 
  23. "Definitions". Microsoft. November 2, 2006. http://www.microsoft.com/interop/msnovellcollab/definitions2.aspx. Retrieved July 5, 2009. 
  24. Steinman, Justin (November 7, 2006). "Novell Answers Questions from the Community". http://www.novell.com/linux/microsoft/faq_opensource.html. Retrieved July 5, 2009. "We maintain that Mono does not infringe any Microsoft patents." 
  25. "Covenant to Downstream Recipients of Moonlight - Microsoft & Novell Interoperability Collaboration". Microsoft. September 28, 2007. http://www.microsoft.com/interop/msnovellcollab/moonlight.mspx. Retrieved March 8, 2008. "“Downstream Recipient” means an entity or individual that uses for its intended purpose a Moonlight Implementation obtained directly from Novell or through an Intermediate Recipient… Microsoft reserves the right to update (including discontinue) the foregoing covenant… “Moonlight Implementation” means only those specific portions of Moonlight 1.0 or Moonlight 1.1 that run only as a plug-in to a browser on a Personal Computer and are not licensed under GPLv3 or a Similar License." 
  26. Stallman, Richard (June 26, 2009). "Why free software shouldn't depend on Mono or C#". Free Software Foundation. http://www.fsf.org/news/dont-depend-on-mono. Retrieved July 2, 2009. "The danger is that Microsoft is probably planning to force all free C# implementations underground some day using software patents. ... We should systematically arrange to depend on the free C# implementations as little as possible. In other words, we should discourage people from writing programs in C#. Therefore, we should not include C# implementations in the default installation of GNU/Linux distributions, and we should distribute and recommend non-C# applications rather than comparable C# applications whenever possible." 
  27. "Microsoft's Empty Promise". Free Software Foundation. 2009-07-16. http://www.fsf.org/news/2009-07-mscp-mono. Retrieved 2009-078-03. "Until that happens, free software developers still should not write software that depends on Mono. C# implementations can still be attacked by Microsoft's patents: the Community Promise is designed to give the company several outs if it wants them. We don't want to see developers' hard work lost to the community if we lose the ability to use Mono, and until we eliminate software patents altogether, using another language is the best way to prevent that from happening." 
  28. "The ECMA C# and CLI Standards". 2009-07-06. http://port25.technet.com/archive/2009/07/06/the-ecma-c-and-cli-standards.aspx. Retrieved 2009-078-03. 


External links

Personal tools

Served in 1.377 secs.