C Sharp (programming language) - Revision history

Ajmullen: /* Name */

2025-06-10T19:08:36Z

Name

← Previous revision		Revision as of 19:08, 10 June 2025
Line 394:		Line 394:
	Its type system is split into two families: Value types, like the built-in numeric types and user-defined structs, which are automatically handed over as copies when used as parameters, and reference types, including arrays, instances of classes, and strings, which only hand over a pointer to the respective object. Due to their special handling of the equality operator and their [[Immutable object\|immutability]], strings will nevertheless behave as if they were values, for all practical purposes. You can even use them as [[Switch statement\|case]] labels. Where necessary, value types will be [[Boxing (computer science)\|boxed]] automatically.<ref>{{cite web\|url=https://learn.microsoft.com/en-us/dotnet/csharp/language-reference/language-specification/types#81-general\|title=Types/General, part of the official C# documentation\|publisher=[[Microsoft]]\|access-date=2024-04-06\|archive-date=March 29, 2024\|archive-url=https://web.archive.org/web/20240329145803/https://learn.microsoft.com/en-us/dotnet/csharp/language-reference/language-specification/types#81-general\|url-status=live}}</ref>		Its type system is split into two families: Value types, like the built-in numeric types and user-defined structs, which are automatically handed over as copies when used as parameters, and reference types, including arrays, instances of classes, and strings, which only hand over a pointer to the respective object. Due to their special handling of the equality operator and their [[Immutable object\|immutability]], strings will nevertheless behave as if they were values, for all practical purposes. You can even use them as [[Switch statement\|case]] labels. Where necessary, value types will be [[Boxing (computer science)\|boxed]] automatically.<ref>{{cite web\|url=https://learn.microsoft.com/en-us/dotnet/csharp/language-reference/language-specification/types#81-general\|title=Types/General, part of the official C# documentation\|publisher=[[Microsoft]]\|access-date=2024-04-06\|archive-date=March 29, 2024\|archive-url=https://web.archive.org/web/20240329145803/https://learn.microsoft.com/en-us/dotnet/csharp/language-reference/language-specification/types#81-general\|url-status=live}}</ref>

	C# supports a strict [[Boolean data type]], <code>bool</code>. Statements that take conditions, such as <code>while</code> and <code>if</code>, require an expression of a type that ~~implements~~ the <code>true</code> ~~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 <code>if (a)</code> require only that <code>a</code> is convertible to bool, allowing <code>a</code> 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 <code>bool</code> can prevent certain types of programming mistakes such as <code>if (a = b)</code> (use of assignment <code>=</code> instead of equality <code>==</code>).		C# supports a strict [[Boolean data type]], <code>bool</code>. Statements that take conditions, such as <code>while</code> and <code>if</code>, require an expression of a type that evaluates to the <code>true</code> boolean value. While C++ also has a Boolean type, it can be freely converted to and from integers, and expressions such as <code>if (a)</code> require only that <code>a</code> is convertible to bool, allowing <code>a</code> 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 <code>bool</code> can prevent certain types of programming mistakes such as <code>if (a = b)</code> (use of assignment <code>=</code> instead of equality <code>==</code>).

	C# is more [[Type safety\|type safe]] than C++. The only [[implicit conversion]]s by default are those that are considered safe, such as widening of integers. This is enforced at compile-time, during [[Just-in-time compilation\|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 constructor]]s and conversion operators, which are both implicit by default.		C# is more [[Type safety\|type safe]] than C++. The only [[implicit conversion]]s by default are those that are considered safe, such as widening of integers. This is enforced at compile-time, during [[Just-in-time compilation\|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 constructor]]s and conversion operators, which are both implicit by default.

MusikBot II: Adding missing protection template (more info)

2025-06-04T03:20:21Z

Adding missing protection template (more info)

← Previous revision		Revision as of 03:20, 4 June 2025
Line 1:		Line 1:
			{{pp\|small=yes}}
	{{Short description\|Programming language}}		{{Short description\|Programming language}}
	{{Correct title\|title=C#\|reason=#}}		{{Correct title\|title=C#\|reason=#}}

Materialscientist: Undid revision 1293864835 by 143.105.119.23 (talk)

2025-06-04T03:12:46Z

Undid revision 1293864835 by 143.105.119.23 (talk)

Show changes

Materialscientist: Protected "C Sharp (programming language)": Persistent disruptive editing ([Edit=Require autoconfirmed or confirmed access] (expires 03:12, 4 July 2025 (UTC)) [Move=Require autoconfirmed or confirmed access] (expires 03:12, 4 July 2025 (UTC)))

2025-06-04T03:12:28Z

Protected "C Sharp (programming language)": Persistent disruptive editing ([Edit=Require autoconfirmed or confirmed access] (expires 03:12, 4 July 2025 (UTC)) [Move=Require autoconfirmed or confirmed access] (expires 03:12, 4 July 2025 (UTC)))

← Previous revision	Revision as of 03:12, 4 June 2025
(No difference)

143.105.119.23: made some minor changes

2025-06-04T03:12:27Z

made some minor changes

Show changes

Patient Zero: Reverted edits by 172.56.102.157 (talk) (HG) (3.4.13)

2025-06-04T03:10:08Z

Reverted edits by 172.56.102.157 (talk) (HG) (3.4.13)

Show changes

172.56.102.157: Undid revision 1293864380 by Joyous! (talk)

2025-06-04T03:09:47Z

Undid revision 1293864380 by Joyous! (talk)

Show changes

Joyous!: Reverted 1 edit by 143.105.119.23 (talk) to last revision by John of Reading

2025-06-04T03:09:02Z

Reverted 1 edit by 143.105.119.23 (talk) to last revision by John of Reading

Show changes

143.105.119.23: Made some slight grammar changes.

2025-06-04T03:08:16Z

Made some slight grammar changes.

Show changes

John of Reading: /* Property */ Typo fixing, replaced: accesor → accessor

2025-05-27T13:06:46Z

Property: Typo fixing, replaced: accesor → accessor

← Previous revision		Revision as of 13:06, 27 May 2025
Line 430:		Line 430:

	===Property===		===Property===
	C# supports classes with [[property (programming)\|properties]]. The properties can be simple ~~accesor~~ functions with a backing field, or implement arbitrary getter and setter functions. A property is read-only if there's no setter. Like with fields, there can be class and instance properties. The underlying methods can be <code>virtual</code> or [[Abstract method#Abstract methods\|<code>abstract</code>]] like any other method.<ref name="properties" />		C# supports classes with [[property (programming)\|properties]]. The properties can be simple accessor functions with a backing field, or implement arbitrary getter and setter functions. A property is read-only if there's no setter. Like with fields, there can be class and instance properties. The underlying methods can be <code>virtual</code> or [[Abstract method#Abstract methods\|<code>abstract</code>]] like any other method.<ref name="properties" />

	Since C# 3.0 the [[syntactic sugar]] of auto-implemented properties is available,<ref name="auto-implemented property">{{cite web\|url=https://docs.microsoft.com/en-us/dotnet/csharp/programming-guide/classes-and-structs/auto-implemented-properties\|title=Auto-Implemented Properties (C# Programming Guide)\|access-date=September 12, 2020\|archive-date=October 29, 2020\|archive-url=https://web.archive.org/web/20201029204026/https://docs.microsoft.com/en-us/dotnet/csharp/programming-guide/classes-and-structs/auto-implemented-properties\|url-status=live}}</ref> where the [[Mutator method\|accessor (getter) and mutator (setter)]] encapsulate operations on a single field of a class.		Since C# 3.0 the [[syntactic sugar]] of auto-implemented properties is available,<ref name="auto-implemented property">{{cite web\|url=https://docs.microsoft.com/en-us/dotnet/csharp/programming-guide/classes-and-structs/auto-implemented-properties\|title=Auto-Implemented Properties (C# Programming Guide)\|access-date=September 12, 2020\|archive-date=October 29, 2020\|archive-url=https://web.archive.org/web/20201029204026/https://docs.microsoft.com/en-us/dotnet/csharp/programming-guide/classes-and-structs/auto-implemented-properties\|url-status=live}}</ref> where the [[Mutator method\|accessor (getter) and mutator (setter)]] encapsulate operations on a single field of a class.

← Previous revision		Revision as of 03:20, 4 June 2025
Line 1:		Line 1:
			{{pp\|small=yes}}
	{{Short description\|Programming language}}		{{Short description\|Programming language}}
	{{Correct title\|title=C#\|reason=#}}		{{Correct title\|title=C#\|reason=#}}