C#

Language Specification

Version 4.0

Notice

© 1999-2010 Microsoft Corporation. All rights reserved.

Microsoft, Windows, Visual Basic, Visual C#, and Visual C++ are either registered trademarks or trademarks of Microsoft Corporation in the U.S.A. and/or other countries/regions.

Other product and company names mentioned herein may be the trademarks of their respective owners.

Table of Contents

1. Introduction 1
1.1 Hello world 1
1.2 Program structure 2
1.3 Types and variables 4
1.4 Expressions 6
1.5 Statements 8
1.6 Classes and objects 12
1.6.1 Members 12
1.6.2 Accessibility 13
1.6.3 Type parameters 13
1.6.4 Base classes 14
1.6.5 Fields 14
1.6.6 Methods 15
1.6.6.1 Parameters 15
1.6.6.2 Method body and local variables 16
1.6.6.3 Static and instance methods 17
1.6.6.4 Virtual, override, and abstract methods 18
1.6.6.5 Method overloading 20
1.6.7 Other function members 21
1.6.7.1 Constructors 22
1.6.7.2 Properties 23
1.6.7.3 Indexers 23
1.6.7.4 Events 24
1.6.7.5 Operators 24
1.6.7.6 Destructors 25
1.7 Structs 25
1.8 Arrays 26
1.9 Interfaces 27
1.10 Enums 29
1.11 Delegates 30
1.12 Attributes 31

2. Lexical structure 33
2.1 Programs 33
2.2 Grammars 33
2.2.1 Grammar notation 33
2.2.2 Lexical grammar 34
2.2.3 Syntactic grammar 34
2.3 Lexical analysis 34
2.3.1 Line terminators 35
2.3.2 Comments 35
2.3.3 White space 37
2.4 Tokens 37
2.4.1 Unicode character escape sequences 37
2.4.2 Identifiers 38
2.4.3 Keywords 39
2.4.4 Literals 40
2.4.4.1 Boolean literals 40
2.4.4.2 Integer literals 40
2.4.4.3 Real literals 41
2.4.4.4 Character literals 42
2.4.4.5 String literals 43
2.4.4.6 The null literal 45
2.4.5 Operators and punctuators 45
2.5 Pre-processing directives 45
2.5.1 Conditional compilation symbols 47
2.5.2 Pre-processing expressions 47
2.5.3 Declaration directives 48
2.5.4 Conditional compilation directives 49
2.5.5 Diagnostic directives 51
2.5.6 Region directives 52
2.5.7 Line directives 52
2.5.8 Pragma directives 53
2.5.8.1 Pragma warning 53

3. Basic concepts 55
3.1 Application Startup 55
3.2 Application termination 56
3.3 Declarations 56
3.4 Members 58
3.4.1 Namespace members 58
3.4.2 Struct members 59
3.4.3 Enumeration members 59
3.4.4 Class members 59
3.4.5 Interface members 60
3.4.6 Array members 60
3.4.7 Delegate members 60
3.5 Member access 60
3.5.1 Declared accessibility 60
3.5.2 Accessibility domains 61
3.5.3 Protected access for instance members 63
3.5.4 Accessibility constraints 64
3.6 Signatures and overloading 65
3.7 Scopes 66
3.7.1 Name hiding 69
3.7.1.1 Hiding through nesting 69
3.7.1.2 Hiding through inheritance 70
3.8 Namespace and type names 71
3.8.1 Fully qualified names 73
3.9 Automatic memory management 73
3.10 Execution order 76

4. Types 77
4.1 Value types 77
4.1.1 The System.ValueType type 78
4.1.2 Default constructors 78
4.1.3 Struct types 79
4.1.4 Simple types 79
4.1.5 Integral types 80
4.1.6 Floating point types 81
4.1.7 The decimal type 82
4.1.8 The bool type 83
4.1.9 Enumeration types 83
4.1.10 Nullable types 83
4.2 Reference types 83
4.2.1 Class types 84
4.2.2 The object type 85
4.2.3 The dynamic type 85
4.2.4 The string type 85
4.2.5 Interface types 85
4.2.6 Array types 85
4.2.7 Delegate types 85
4.3 Boxing and unboxing 86
4.3.1 Boxing conversions 86
4.3.2 Unboxing conversions 87
4.4 Constructed types 88
4.4.1 Type arguments 89
4.4.2 Open and closed types 89
4.4.3 Bound and unbound types 89
4.4.4 Satisfying constraints 89
4.5 Type parameters 90
4.6 Expression tree types 91
4.7 The dynamic type 92

5. Variables 93
5.1 Variable categories 93
5.1.1 Static variables 93
5.1.2 Instance variables 93
5.1.2.1 Instance variables in classes 93
5.1.2.2 Instance variables in structs 94
5.1.3 Array elements 94
5.1.4 Value parameters 94
5.1.5 Reference parameters 94
5.1.6 Output parameters 94
5.1.7 Local variables 95
5.2 Default values 96
5.3 Definite assignment 96
5.3.1 Initially assigned variables 97
5.3.2 Initially unassigned variables 97
5.3.3 Precise rules for determining definite assignment 97
5.3.3.1 General rules for statements 98
5.3.3.2 Block statements, checked, and unchecked statements 98
5.3.3.3 Expression statements 98
5.3.3.4 Declaration statements 98
5.3.3.5 If statements 98
5.3.3.6 Switch statements 99
5.3.3.7 While statements 99
5.3.3.8 Do statements 99
5.3.3.9 For statements 100
5.3.3.10 Break, continue, and goto statements 100
5.3.3.11 Throw statements 100
5.3.3.12 Return statements 100
5.3.3.13 Try-catch statements 100
5.3.3.14 Try-finally statements 101
5.3.3.15 Try-catch-finally statements 101
5.3.3.16 Foreach statements 102
5.3.3.17 Using statements 102
5.3.3.18 Lock statements 102
5.3.3.19 Yield statements 103
5.3.3.20 General rules for simple expressions 103
5.3.3.21 General rules for expressions with embedded expressions 103
5.3.3.22 Invocation expressions and object creation expressions 103
5.3.3.23 Simple assignment expressions 104
5.3.3.24 && expressions 104
5.3.3.25 || expressions 105
5.3.3.26 ! expressions 106
5.3.3.27 ?? expressions 106
5.3.3.28 ?: expressions 106
5.3.3.29 Anonymous functions 107
5.4 Variable references 107
5.5 Atomicity of variable references 107

6. Conversions 109
6.1 Implicit conversions 109
6.1.1 Identity conversion 109
6.1.2 Implicit numeric conversions 110
6.1.3 Implicit enumeration conversions 110
6.1.4 Implicit nullable conversions 110
6.1.5 Null literal conversions 111
6.1.6 Implicit reference conversions 111
6.1.7 Boxing conversions 111
6.1.8 Implicit dynamic conversions 112
6.1.9 Implicit constant expression conversions 112
6.1.10 Implicit conversions involving type parameters 112
6.1.11 User-defined implicit conversions 113
6.1.12 Anonymous function conversions and method group conversions 113
6.2 Explicit conversions 113
6.2.1 Explicit numeric conversions 114
6.2.2 Explicit enumeration conversions 115
6.2.3 Explicit nullable conversions 115
6.2.4 Explicit reference conversions 116
6.2.5 Unboxing conversions 117
6.2.6 Explicit dynamic conversions 117
6.2.7 Explicit conversions involving type parameters 118
6.2.8 User-defined explicit conversions 119
6.3 Standard conversions 119
6.3.1 Standard implicit conversions 119
6.3.2 Standard explicit conversions 119
6.4 User-defined conversions 119
6.4.1 Permitted user-defined conversions 119
6.4.2 Lifted conversion operators 120
6.4.3 Evaluation of user-defined conversions 120
6.4.4 User-defined implicit conversions 121
6.4.5 User-defined explicit conversions 122
6.5 Anonymous function conversions 123
6.5.1 Evaluation of anonymous function conversions to delegate types 124
6.5.2 Evaluation of anonymous function conversions to expression tree types 124
6.5.3 Implementation example 124
6.6 Method group conversions 127

7. Expressions 131
7.1 Expression classifications 131
7.1.1 Values of expressions 132
7.2 Static and Dynamic Binding 132
7.2.1 Binding-time 133
7.2.2 Dynamic binding 133
7.2.3 Types of constituent expressions 133
7.3 Operators 134
7.3.1 Operator precedence and associativity 134
7.3.2 Operator overloading 135
7.3.3 Unary operator overload resolution 136
7.3.4 Binary operator overload resolution 137
7.3.5 Candidate user-defined operators 137
7.3.6 Numeric promotions 137
7.3.6.1 Unary numeric promotions 138
7.3.6.2 Binary numeric promotions 138
7.3.7 Lifted operators 139
7.4 Member lookup 139
7.4.1 Base types 141
7.5 Function members 141
7.5.1 Argument lists 143
7.5.1.1 Corresponding parameters 144
7.5.1.2 Run-time evaluation of argument lists 145
7.5.2 Type inference 147
7.5.2.1 The first phase 147
7.5.2.2 The second phase 148
7.5.2.3 Input types 148
7.5.2.4 Output types 148
7.5.2.5 Dependence 148
7.5.2.6 Output type inferences 148
7.5.2.7 Explicit parameter type inferences 148
7.5.2.8 Exact inferences 149
7.5.2.9 Lower-bound inferences 149
7.5.2.10 Upper-bound inferences 150
7.5.2.11 Fixing 150
7.5.2.12 Inferred return type 150
7.5.2.13 Type inference for conversion of method groups 151
7.5.2.14 Finding the best common type of a set of expressions 152
7.5.3 Overload resolution 152
7.5.3.1 Applicable function member 153
7.5.3.2 Better function member 153
7.5.3.3 Better conversion from expression 154
7.5.3.4 Better conversion from type 155
7.5.3.5 Better conversion target 155
7.5.3.6 Overloading in generic classes 155
7.5.4 Compile-time checking of dynamic overload resolution 155
7.5.5 Function member invocation 156
7.5.5.1 Invocations on boxed instances 157
7.6 Primary expressions 157
7.6.1 Literals 158
7.6.2 Simple names 158
7.6.2.1 Invariant meaning in blocks 159
7.6.3 Parenthesized expressions 160
7.6.4 Member access 161
7.6.4.1 Identical simple names and type names 162
7.6.4.2 Grammar ambiguities 163
7.6.5 Invocation expressions 164
7.6.5.1 Method invocations 164
7.6.5.2 Extension method invocations 165
7.6.5.3 Delegate invocations 168
7.6.6 Element access 168
7.6.6.1 Array access 168
7.6.6.2 Indexer access 169
7.6.7 This access 170
7.6.8 Base access 170
7.6.9 Postfix increment and decrement operators 171
7.6.10 The new operator 172
7.6.10.1 Object creation expressions 172
7.6.10.2 Object initializers 173
7.6.10.3 Collection initializers 175
7.6.10.4 Array creation expressions 176
7.6.10.5 Delegate creation expressions 178
7.6.10.6 Anonymous object creation expressions 180
7.6.11 The typeof operator 181
7.6.12 The checked and unchecked operators 183
7.6.13 Default value expressions 185
7.6.14 Anonymous method expressions 185
7.7 Unary operators 186
7.7.1 Unary plus operator 186
7.7.2 Unary minus operator 186
7.7.3 Logical negation operator 187
7.7.4 Bitwise complement operator 187
7.7.5 Prefix increment and decrement operators 187
7.7.6 Cast expressions 188
7.8 Arithmetic operators 189
7.8.1 Multiplication operator 189
7.8.2 Division operator 190
7.8.3 Remainder operator 191
7.8.4 Addition operator 192
7.8.5 Subtraction operator 194
7.9 Shift operators 195
7.10 Relational and type-testing operators 197
7.10.1 Integer comparison operators 197
7.10.2 Floating-point comparison operators 198
7.10.3 Decimal comparison operators 199
7.10.4 Boolean equality operators 199
7.10.5 Enumeration comparison operators 199
7.10.6 Reference type equality operators 199
7.10.7 String equality operators 201
7.10.8 Delegate equality operators 201
7.10.9 Equality operators and null 202
7.10.10 The is operator 202
7.10.11 The as operator 202
7.11 Logical operators 203
7.11.1 Integer logical operators 204
7.11.2 Enumeration logical operators 204
7.11.3 Boolean logical operators 204
7.11.4 Nullable boolean logical operators 204
7.12 Conditional logical operators 205
7.12.1 Boolean conditional logical operators 206
7.12.2 User-defined conditional logical operators 206
7.13 The null coalescing operator 206
7.14 Conditional operator 207
7.15 Anonymous function expressions 208
7.15.1 Anonymous function signatures 210
7.15.2 Anonymous function bodies 210
7.15.3 Overload resolution 211
7.15.4 Anonymous functions and dynamic binding 211
7.15.5 Outer variables 211
7.15.5.1 Captured outer variables 212
7.15.5.2 Instantiation of local variables 212
7.15.6 Evaluation of anonymous function expressions 214
7.16 Query expressions 215
7.16.1 Ambiguities in query expressions 216
7.16.2 Query expression translation 216
7.16.2.1 Select and groupby clauses with continuations 217
7.16.2.2 Explicit range variable types 217
7.16.2.3 Degenerate query expressions 218
7.16.2.4 From, let, where, join and orderby clauses 218
7.16.2.5 Select clauses 221
7.16.2.6 Groupby clauses 222
7.16.2.7 Transparent identifiers 222
7.16.3 The query expression pattern 223
7.17 Assignment operators 224
7.17.1 Simple assignment 225
7.17.2 Compound assignment 227
7.17.3 Event assignment 228
7.18 Expression 228
7.19 Constant expressions 228
7.20 Boolean expressions 230

8. Statements 231
8.1 End points and reachability 231
8.2 Blocks 233
8.2.1 Statement lists 233
8.3 The empty statement 234
8.4 Labeled statements 234
8.5 Declaration statements 235
8.5.1 Local variable declarations 235
8.5.2 Local constant declarations 236
8.6 Expression statements 237
8.7 Selection statements 237
8.7.1 The if statement 237
8.7.2 The switch statement 238
8.8 Iteration statements 241
8.8.1 The while statement 242
8.8.2 The do statement 242
8.8.3 The for statement 243
8.8.4 The foreach statement 244
8.9 Jump statements 246
8.9.1 The break statement 247
8.9.2 The continue statement 248
8.9.3 The goto statement 248
8.9.4 The return statement 250
8.9.5 The throw statement 250
8.10 The try statement 251
8.11 The checked and unchecked statements 254
8.12 The lock statement 254
8.13 The using statement 255
8.14 The yield statement 257

9. Namespaces 259
9.1 Compilation units 259
9.2 Namespace declarations 259
9.3 Extern aliases 260
9.4 Using directives 261
9.4.1 Using alias directives 262
9.4.2 Using namespace directives 264
9.5 Namespace members 266
9.6 Type declarations 266
9.7 Namespace alias qualifiers 267
9.7.1 Uniqueness of aliases 268

10. Classes 269
10.1 Class declarations 269
10.1.1 Class modifiers 269
10.1.1.1 Abstract classes 270
10.1.1.2 Sealed classes 270
10.1.1.3 Static classes 270
10.1.2 Partial modifier 271
10.1.3 Type parameters 271
10.1.4 Class base specification 272
10.1.4.1 Base classes 272
10.1.4.2 Interface implementations 274
10.1.5 Type parameter constraints 274
10.1.6 Class body 278
10.2 Partial types 278
10.2.1 Attributes 278
10.2.2 Modifiers 279
10.2.3 Type parameters and constraints 279
10.2.4 Base class 280
10.2.5 Base interfaces 280
10.2.6 Members 280
10.2.7 Partial methods 281
10.2.8 Name binding 283
10.3 Class members 283
10.3.1 The instance type 285
10.3.2 Members of constructed types 285
10.3.3 Inheritance 286
10.3.4 The new modifier 287
10.3.5 Access modifiers 287
10.3.6 Constituent types 287
10.3.7 Static and instance members 287
10.3.8 Nested types 288
10.3.8.1 Fully qualified name 289
10.3.8.2 Declared accessibility 289
10.3.8.3 Hiding 289
10.3.8.4 this access 290
10.3.8.5 Access to private and protected members of the containing type 290
10.3.8.6 Nested types in generic classes 291
10.3.9 Reserved member names 292
10.3.9.1 Member names reserved for properties 292
10.3.9.2 Member names reserved for events 293
10.3.9.3 Member names reserved for indexers 293
10.3.9.4 Member names reserved for destructors 293
10.4 Constants 293
10.5 Fields 295
10.5.1 Static and instance fields 296
10.5.2 Readonly fields 297
10.5.2.1 Using static readonly fields for constants 297
10.5.2.2 Versioning of constants and static readonly fields 298
10.5.3 Volatile fields 298
10.5.4 Field initialization 299
10.5.5 Variable initializers 300
10.5.5.1 Static field initialization 301
10.5.5.2 Instance field initialization 302
10.6 Methods 302
10.6.1 Method parameters 304
10.6.1.1 Value parameters 306
10.6.1.2 Reference parameters 306
10.6.1.3 Output parameters 307
10.6.1.4 Parameter arrays 308
10.6.2 Static and instance methods 310
10.6.3 Virtual methods 310
10.6.4 Override methods 312
10.6.5 Sealed methods 314
10.6.6 Abstract methods 315
10.6.7 External methods 316
10.6.8 Partial methods 317
10.6.9 Extension methods 317
10.6.10 Method body 318
10.6.11 Method overloading 318
10.7 Properties 318
10.7.1 Static and instance properties 320
10.7.2 Accessors 320
10.7.3 Automatically implemented properties 325
10.7.4 Accessibility 325
10.7.5 Virtual, sealed, override, and abstract accessors 327
10.8 Events 328
10.8.1 Field-like events 330
10.8.2 Event accessors 332
10.8.3 Static and instance events 333
10.8.4 Virtual, sealed, override, and abstract accessors 333
10.9 Indexers 333
10.9.1 Indexer overloading 337
10.10 Operators 337
10.10.1 Unary operators 339
10.10.2 Binary operators 339
10.10.3 Conversion operators 340
10.11 Instance constructors 342
10.11.1 Constructor initializers 343
10.11.2 Instance variable initializers 344
10.11.3 Constructor execution 344
10.11.4 Default constructors 346
10.11.5 Private constructors 346
10.11.6 Optional instance constructor parameters 347
10.12 Static constructors 347
10.13 Destructors 349
10.14 Iterators 351
10.14.1 Enumerator interfaces 351
10.14.2 Enumerable interfaces 351
10.14.3 Yield type 351
10.14.4 Enumerator objects 351
10.14.4.1 The MoveNext method 352
10.14.4.2 The Current property 353
10.14.4.3 The Dispose method 353
10.14.5 Enumerable objects 353
10.14.5.1 The GetEnumerator method 354
10.14.6 Implementation example 354

11. Structs 361
11.1 Struct declarations 361
11.1.1 Struct modifiers 361
11.1.2 Partial modifier 362
11.1.3 Struct interfaces 362
11.1.4 Struct body 362
11.2 Struct members 362
11.3 Class and struct differences 362
11.3.1 Value semantics 363
11.3.2 Inheritance 364
11.3.3 Assignment 364
11.3.4 Default values 364
11.3.5 Boxing and unboxing 365
11.3.6 Meaning of this 366
11.3.7 Field initializers 366
11.3.8 Constructors 367
11.3.9 Destructors 368
11.3.10 Static constructors 368
11.4 Struct examples 368
11.4.1 Database integer type 368
11.4.2 Database boolean type 370

12. Arrays 373
12.1 Array types 373
12.1.1 The System.Array type 374
12.1.2 Arrays and the generic IList interface 374
12.2 Array creation 374
12.3 Array element access 375
12.4 Array members 375
12.5 Array covariance 375
12.6 Array initializers 375

13. Interfaces 379
13.1 Interface declarations 379
13.1.1 Interface modifiers 379
13.1.2 Partial modifier 379
13.1.3 Variant type parameter lists 380
13.1.3.1 Variance safety 380
13.1.3.2 Variance conversion 381
13.1.4 Base interfaces 381
13.1.5 Interface body 382
13.2 Interface members 382
13.2.1 Interface methods 383
13.2.2 Interface properties 383
13.2.3 Interface events 384
13.2.4 Interface indexers 384
13.2.5 Interface member access 384
13.3 Fully qualified interface member names 386
13.4 Interface implementations 386
13.4.1 Explicit interface member implementations 387
13.4.2 Uniqueness of implemented interfaces 389
13.4.3 Implementation of generic methods 390
13.4.4 Interface mapping 391
13.4.5 Interface implementation inheritance 394
13.4.6 Interface re-implementation 395
13.4.7 Abstract classes and interfaces 396

14. Enums 399
14.1 Enum declarations 399
14.2 Enum modifiers 399
14.3 Enum members 400
14.4 The System.Enum type 402
14.5 Enum values and operations 402

15. Delegates 403
15.1 Delegate declarations 403
15.2 Delegate compatibility 405
15.3 Delegate instantiation 405
15.4 Delegate invocation 406

16. Exceptions 409
16.1 Causes of exceptions 409
16.2 The System.Exception class 409
16.3 How exceptions are handled 409
16.4 Common Exception Classes 410

17. Attributes 411
17.1 Attribute classes 411
17.1.1 Attribute usage 411
17.1.2 Positional and named parameters 412
17.1.3 Attribute parameter types 413
17.2 Attribute specification 413
17.3 Attribute instances 418
17.3.1 Compilation of an attribute 418
17.3.2 Run-time retrieval of an attribute instance 419
17.4 Reserved attributes 419
17.4.1 The AttributeUsage attribute 419
17.4.2 The Conditional attribute 420
17.4.2.1 Conditional methods 420
17.4.2.2 Conditional attribute classes 422
17.4.3 The Obsolete attribute 423
17.5 Attributes for Interoperation 424
17.5.1 Interoperation with COM and Win32 components 424
17.5.2 Interoperation with other .NET languages 425
17.5.2.1 The IndexerName attribute 425

18. Unsafe code 427
18.1 Unsafe contexts 427
18.2 Pointer types 429
18.3 Fixed and moveable variables 432
18.4 Pointer conversions 432
18.4.1 Pointer arrays 433
18.5 Pointers in expressions 434
18.5.1 Pointer indirection 435
18.5.2 Pointer member access 435
18.5.3 Pointer element access 436
18.5.4 The address-of operator 436
18.5.5 Pointer increment and decrement 437
18.5.6 Pointer arithmetic 437
18.5.7 Pointer comparison 438
18.5.8 The sizeof operator 439
18.6 The fixed statement 439
18.7 Fixed size buffers 443
18.7.1 Fixed size buffer declarations 443
18.7.2 Fixed size buffers in expressions 444
18.7.3 Definite assignment checking 445
18.8 Stack allocation 445
18.9 Dynamic memory allocation 446

A. Documentation comments 449
A.1 Introduction 449
A.2 Recommended tags 450
A.2.1 451
A.2.2 451
A.2.3 452
A.2.4 452
A.2.5 453
A.2.6 453
A.2.7 454
A.2.8 455
A.2.9 455
A.2.10 455
A.2.11 456
A.2.12 456
A.2.13 457
A.2.14 457
A.2.15 457
A.2.16 458
A.2.17 458
A.2.18 458
A.3 Processing the documentation file 459
A.3.1 ID string format 459
A.3.2 ID string examples 460
A.4 An example 464
A.4.1 C# source code 464
A.4.2 Resulting XML 466

B. Grammar 470
B.1 Lexical grammar 470
B.1.1 Line terminators 470
B.1.2 Comments 470
B.1.3 White space 471
B.1.4 Tokens 471
B.1.5 Unicode character escape sequences 471
B.1.6 Identifiers 471
B.1.7 Keywords 472
B.1.8 Literals 473
B.1.9 Operators and punctuators 475
B.1.10 Pre-processing directives 475
B.2 Syntactic grammar 477
B.2.1 Basic concepts 477
B.2.2 Types 478
B.2.3 Variables 479
B.2.4 Expressions 479
B.2.5 Statements 486
B.2.6 Namespaces 489
B.2.7 Classes 490
B.2.8 Structs 497
B.2.9 Arrays 498
B.2.10 Interfaces 498
B.2.11 Enums 499
B.2.12 Delegates 500
B.2.13 Attributes 500
B.3 Grammar extensions for unsafe code 502

C. References 505
Introduction

C# (pronounced “See Sharp”) is a simple, modern, object-oriented, and type-safe programming language. C# has its roots in the C family of languages and will be immediately familiar to C, C++, and Java programmers. C# is standardized by ECMA International as the ECMA-334 standard and by ISO/IEC as the ISO/IEC 23270 standard. Microsoft’s C# compiler for the .NET Framework is a conforming implementation of both of these standards.

C# is an object-oriented language, but C# further includes support for component-oriented programming. Contemporary software design increasingly relies on software components in the form of self-contained and self-describing packages of functionality. Key to such components is that they present a programming model with properties, methods, and events; they have attributes that provide declarative information about the component; and they incorporate their own documentation. C# provides language constructs to directly support these concepts, making C# a very natural language in which to create and use software components.

Several C# features aid in the construction of robust and durable applications: Garbage collection automatically reclaims memory occupied by unused objects; exception handling provides a structured and extensible approach to error detection and recovery; and the type-safe design of the language makes it impossible to read from uninitialized variables, to index arrays beyond their bounds, or to perform unchecked type casts.

C# has a unified type system. All C# types, including primitive types such as int and double, inherit from a single root object type. Thus, all types share a set of common operations, and values of any type can be stored, transported, and operated upon in a consistent manner. Furthermore, C# supports both user-defined reference types and value types, allowing dynamic allocation of objects as well as in-line storage of lightweight structures.

To ensure that C# programs and libraries can evolve over time in a compatible manner, much emphasis has been placed on versioning in C#’s design. Many programming languages pay little attention to this issue, and, as a result, programs written in those languages break more often than necessary when newer versions of dependent libraries are introduced. Aspects of C#’s design that were directly influenced by versioning considerations include the separate virtual and override modifiers, the rules for method overload resolution, and support for explicit interface member declarations.

The rest of this chapter describes the essential features of the C# language. Although later chapters describe rules and exceptions in a detail-oriented and sometimes mathematical manner, this chapter strives for clarity and brevity at the expense of completeness. The intent is to provide the reader with an introduction to the language that will facilitate the writing of early programs and the reading of later chapters.

1 Hello world

The “Hello, World” program is traditionally used to introduce a programming language. Here it is in C#:

using System;

class Hello
{
static void Main() { Console.WriteLine("Hello, World"); }
}

C# source files typically have the file extension .cs. Assuming that the “Hello, World” program is stored in the file hello.cs, the program can be compiled with the Microsoft C# compiler using the command line

csc hello.cs

which produces an executable assembly named hello.exe. The output produced by this application when it is run is

Hello, World

The “Hello, World” program starts with a using directive that references the System namespace. Namespaces provide a hierarchical means of organizing C# programs and libraries. Namespaces contain types and other namespaces—for example, the System namespace contains a number of types, such as the Console class referenced in the program, and a number of other namespaces, such as IO and Collections. A using directive that references a given namespace enables unqualified use of the types that are members of that namespace. Because of the using directive, the program can use Console.WriteLine as shorthand for System.Console.WriteLine.

The Hello class declared by the “Hello, World” program has a single member, the method named Main. The Main method is declared with the static modifier. While instance methods can reference a particular enclosing object instance using the keyword this, static methods operate without reference to a particular object. By convention, a static method named Main serves as the entry point of a program.

The output of the program is produced by the WriteLine method of the Console class in the System namespace. This class is provided by the .NET Framework class libraries, which, by default, are automatically referenced by the Microsoft C# compiler. Note that C# itself does not have a separate runtime library. Instead, the .NET Framework is the runtime library of C#.

2 Program structure

The key organizational concepts in C# are programs, namespaces, types, members, and assemblies. C# programs consist of one or more source files. Programs declare types, which contain members and can be organized into namespaces. Classes and interfaces are examples of types. Fields, methods, properties, and events are examples of members. When C# programs are compiled, they are physically packaged into assemblies. Assemblies typically have the file extension .exe or .dll, depending on whether they implement applications or libraries.

The example

using System;

namespace Acme.Collections
{
public class Stack { Entry top;

public void Push(object data) { top = new Entry(top, data); }

public object Pop() { if (top == null) throw new InvalidOperationException(); object result = top.data; top = top.next; return result; }

class Entry { public Entry next; public object data;

public Entry(Entry next, object data) { this.next = next; this.data = data; } } }
}

declares a class named Stack in a namespace called Acme.Collections. The fully qualified name of this class is Acme.Collections.Stack. The class contains several members: a field named top, two methods named Push and Pop, and a nested class named Entry. The Entry class further contains three members: a field named next, a field named data, and a constructor. Assuming that the source code of the example is stored in the file acme.cs, the command line

csc /t:library acme.cs

compiles the example as a library (code without a Main entry point) and produces an assembly named acme.dll.

Assemblies contain executable code in the form of Intermediate Language (IL) instructions, and symbolic information in the form of metadata. Before it is executed, the IL code in an assembly is automatically converted to processor-specific code by the Just-In-Time (JIT) compiler of .NET Common Language Runtime.

Because an assembly is a self-describing unit of functionality containing both code and metadata, there is no need for #include directives and header files in C#. The public types and members contained in a particular assembly are made available in a C# program simply by referencing that assembly when compiling the program. For example, this program uses the Acme.Collections.Stack class from the acme.dll assembly:

using System; using Acme.Collections;

class Test
{
static void Main() { Stack s = new Stack(); s.Push(1); s.Push(10); s.Push(100); Console.WriteLine(s.Pop()); Console.WriteLine(s.Pop()); Console.WriteLine(s.Pop()); }
}

If the program is stored in the file test.cs, when test.cs is compiled, the acme.dll assembly can be referenced using the compiler’s /r option:

csc /r:acme.dll test.cs

This creates an executable assembly named test.exe, which, when run, produces the output:

100
10
1

C# permits the source text of a program to be stored in several source files. When a multi-file C# program is compiled, all of the source files are processed together, and the source files can freely reference each other—conceptually, it is as if all the source files were concatenated into one large file before being processed. Forward declarations are never needed in C# because, with very few exceptions, declaration order is insignificant. C# does not limit a source file to declaring only one public type nor does it require the name of the source file to match a type declared in the source file.

3 Types and variables

There are two kinds of types in C#: value types and reference types. Variables of value types directly contain their data whereas variables of reference types store references to their data, the latter being known as objects. With reference types, it is possible for two variables to reference the same object and thus possible for operations on one variable to affect the object referenced by the other variable. With value types, the variables each have their own copy of the data, and it is not possible for operations on one to affect the other (except in the case of ref and out parameter variables).

C#’s value types are further divided into simple types, enum types, struct types, and nullable types, and C#’s reference types are further divided into class types, interface types, array types, and delegate types.

The following table provides an overview of C#’s type system.

|Category |Description |
|Value |Simple types |Signed integral: sbyte, short, int, long |
|types | | |
| | |Unsigned integral: byte, ushort, uint, ulong |
| | |Unicode characters: char |
| | |IEEE floating point: float, double |
| | |High-precision decimal: decimal |
| | |Boolean: bool |
| |Enum types |User-defined types of the form enum E {...} |
| |Struct types |User-defined types of the form struct S {...} |
| |Nullable types |Extensions of all other value types with a null value |
|Reference |Class types |Ultimate base class of all other types: object |
|types | | |
| | |Unicode strings: string |
| | |User-defined types of the form class C {...} |
| |Interface types |User-defined types of the form interface I {...} |
| |Array types |Single- and multi-dimensional, for example, int[] and int[,] |
| |Delegate types |User-defined types of the form e.g. delegate int D(...) |

The eight integral types provide support for 8-bit, 16-bit, 32-bit, and 64-bit values in signed or unsigned form.

The two floating point types, float and double, are represented using the 32-bit single-precision and 64-bit double-precision IEEE 754 formats.

The decimal type is a 128-bit data type suitable for financial and monetary calculations.

C#’s bool type is used to represent boolean values—values that are either true or false.

Character and string processing in C# uses Unicode encoding. The char type represents a UTF-16 code unit, and the string type represents a sequence of UTF-16 code units.

The following table summarizes C#’s numeric types.

|Category |Bits |Type |Range/Precision |
|Signed integral |8 |sbyte |–128...127 |
| |16 |short |–32,768...32,767 |
| |32 |int |–2,147,483,648...2,147,483,647 |
| |64 |long |–9,223,372,036,854,775,808...9,223,372,036,854,775,807 |
|Unsigned integral |8 |byte |0...255 |
| |16 |ushort |0...65,535 |
| |32 |uint |0...4,294,967,295 |
| |64 |ulong |0...18,446,744,073,709,551,615 |
|Floating point |32 |float |1.5 × 10−45 to 3.4 × 1038, 7-digit precision |
| |64 |double |5.0 × 10−324 to 1.7 × 10308, 15-digit precision |
|Decimal |128 |decimal |1.0 × 10−28 to 7.9 × 1028, 28-digit precision |

C# programs use type declarations to create new types. A type declaration specifies the name and the members of the new type. Five of C#’s categories of types are user-definable: class types, struct types, interface types, enum types, and delegate types.

A class type defines a data structure that contains data members (fields) and function members (methods, properties, and others). Class types support single inheritance and polymorphism, mechanisms whereby derived classes can extend and specialize base classes.

A struct type is similar to a class type in that it represents a structure with data members and function members. However, unlike classes, structs are value types and do not require heap allocation. Struct types do not support user-specified inheritance, and all struct types implicitly inherit from type object.

An interface type defines a contract as a named set of public function members. A class or struct that implements an interface must provide implementations of the interface’s function members. An interface may inherit from multiple base interfaces, and a class or struct may implement multiple interfaces.

A delegate type represents references to methods with a particular parameter list and return type. Delegates make it possible to treat methods as entities that can be assigned to variables and passed as parameters. Delegates are similar to the concept of function pointers found in some other languages, but unlike function pointers, delegates are object-oriented and type-safe.

Class, struct, interface and delegate types all support generics, whereby they can be parameterized with other types.

An enum type is a distinct type with named constants. Every enum type has an underlying type, which must be one of the eight integral types. The set of values of an enum type is the same as the set of values of the underlying type.

C# supports single- and multi-dimensional arrays of any type. Unlike the types listed above, array types do not have to be declared before they can be used. Instead, array types are constructed by following a type name with square brackets. For example, int[] is a single-dimensional array of int, int[,] is a two-dimensional array of int, and int[][] is a single-dimensional array of single-dimensional arrays of int.

Nullable types also do not have to be declared before they can be used. For each non-nullable value type T there is a corresponding nullable type T?, which can hold an additional value null. For instance, int? is a type that can hold any 32 bit integer or the value null.

C#’s type system is unified such that a value of any type can be treated as an object. Every type in C# directly or indirectly derives from the object class type, and object is the ultimate base class of all types. Values of reference types are treated as objects simply by viewing the values as type object. Values of value types are treated as objects by performing boxing and unboxing operations. In the following example, an int value is converted to object and back again to int.

using System;

class Test
{
static void Main() { int i = 123; object o = i; // Boxing int j = (int)o; // Unboxing }
}

When a value of a value type is converted to type object, an object instance, also called a “box,” is allocated to hold the value, and the value is copied into that box. Conversely, when an object reference is cast to a value type, a check is made that the referenced object is a box of the correct value type, and, if the check succeeds, the value in the box is copied out.

C#’s unified type system effectively means that value types can become objects “on demand.” Because of the unification, general-purpose libraries that use type object can be used with both reference types and value types.

There are several kinds of variables in C#, including fields, array elements, local variables, and parameters. Variables represent storage locations, and every variable has a type that determines what values can be stored in the variable, as shown by the following table.

|Type of Variable |Possible Contents |
|Non-nullable value type |A value of that exact type |
|Nullable value type |A null value or a value of that exact type |
|object |A null reference, a reference to an object of any reference type, or a reference to a boxed value |
| |of any value type |
|Class type |A null reference, a reference to an instance of that class type, or a reference to an instance of |
| |a class derived from that class type |
|Interface type |A null reference, a reference to an instance of a class type that implements that interface type, |
| |or a reference to a boxed value of a value type that implements that interface type |
|Array type |A null reference, a reference to an instance of that array type, or a reference to an instance of |
| |a compatible array type |
|Delegate type |A null reference or a reference to an instance of that delegate type |

4 Expressions

Expressions are constructed from operands and operators. The operators of an expression indicate which operations to apply to the operands. Examples of operators include +, -, *, /, and new. Examples of operands include literals, fields, local variables, and expressions.

When an expression contains multiple operators, the precedence of the operators controls the order in which the individual operators are evaluated. For example, the expression x + y * z is evaluated as x + (y * z) because the * operator has higher precedence than the + operator.

Most operators can be overloaded. Operator overloading permits user-defined operator implementations to be specified for operations where one or both of the operands are of a user-defined class or struct type.

The following table summarizes C#’s operators, listing the operator categories in order of precedence from highest to lowest. Operators in the same category have equal precedence.

|Category |Expression |Description |
|Primary |x.m |Member access |
| |x(...) |Method and delegate invocation |
| |x[...] |Array and indexer access |
| |x++ |Post-increment |
| |x-- |Post-decrement |
| |new T(...) |Object and delegate creation |
| |new T(...){...} |Object creation with initializer |
| |new {...} |Anonymous object initializer |
| |new T[...] |Array creation |
| |typeof(T) |Obtain System.Type object for T |
| |checked(x) |Evaluate expression in checked context |
| |unchecked(x) |Evaluate expression in unchecked context |
| |default(T) |Obtain default value of type T |
| |delegate {...} |Anonymous function (anonymous method) |
|Unary |+x |Identity |
| |-x |Negation |
| |!x |Logical negation |
| |~x |Bitwise negation |
| |++x |Pre-increment |
| |--x |Pre-decrement |
| |(T)x |Explicitly convert x to type T |
|Multiplicative |x * y |Multiplication |
| |x / y |Division |
| |x % y |Remainder |
|Additive |x + y |Addition, string concatenation, delegate combination |
| |x – y |Subtraction, delegate removal |

|Shift |x > y |Shift right |
|Relational and type testing|x < y |Less than |
| |x > y |Greater than |
| |x = y |Greater than or equal |
| |x is T |Return true if x is a T, false otherwise |
| |x as T |Return x typed as T, or null if x is not a T |
|Equality |x == y |Equal |
| |x != y |Not equal |
|Logical AND |x & y |Integer bitwise AND, boolean logical AND |
|Logical XOR |x ^ y |Integer bitwise XOR, boolean logical XOR |
|Logical OR |x | y |Integer bitwise OR, boolean logical OR |
|Conditional AND |x && y |Evaluates y only if x is true |
|Conditional OR |x || y |Evaluates y only if x is false |
|Null coalescing |X ?? y |Evaluates to y if x is null, to x otherwise |
|Conditional |x ? y : z |Evaluates y if x is true, z if x is false |
|Assignment or anonymous |x = y |Assignment |
|function | | |
| |x op= y |Compound assignment; supported operators are |
| | |*= /= %= += -= = &= ^= |= |
| |(T x) => y |Anonymous function (lambda expression) |

5 Statements

The actions of a program are expressed using statements. C# supports several different kinds of statements, a number of which are defined in terms of embedded statements.

A block permits multiple statements to be written in contexts where a single statement is allowed. A block consists of a list of statements written between the delimiters { and }.

Declaration statements are used to declare local variables and constants.

Expression statements are used to evaluate expressions. Expressions that can be used as statements include method invocations, object allocations using the new operator, assignments using = and the compound assignment operators, and increment and decrement operations using the ++ and -- operators.

Selection statements are used to select one of a number of possible statements for execution based on the value of some expression. In this group are the if and switch statements.

Iteration statements are used to repeatedly execute an embedded statement. In this group are the while, do, for, and foreach statements.

Jump statements are used to transfer control. In this group are the break, continue, goto, throw, return, and yield statements.

The try...catch statement is used to catch exceptions that occur during execution of a block, and the try...finally statement is used to specify finalization code that is always executed, whether an exception occurred or not.

The checked and unchecked statements are used to control the overflow checking context for integral-type arithmetic operations and conversions.

The lock statement is used to obtain the mutual-exclusion lock for a given object, execute a statement, and then release the lock.

The using statement is used to obtain a resource, execute a statement, and then dispose of that resource.

The following table lists C#’s statements and provides an example for each one.

|Statement |Example |
|Local variable declaration |static void Main() { |
| |int a; |
| |int b = 2, c = 3; |
| |a = 1; |
| |Console.WriteLine(a + b + c); |
| |} |
|Local constant declaration |static void Main() { |
| |const float pi = 3.1415927f; |
| |const int r = 25; |
| |Console.WriteLine(pi * r * r); |
| |} |
|Expression statement |static void Main() { |
| |int i; |
| |i = 123; // Expression statement |
| |Console.WriteLine(i); // Expression statement |
| |i++; // Expression statement |
| |Console.WriteLine(i); // Expression statement |
| |} |
|if statement |static void Main(string[] args) { |
| |if (args.Length == 0) { |
| |Console.WriteLine("No arguments"); |
| |} |
| |else { |
| |Console.WriteLine("One or more arguments"); |
| |} |
| |} |

|switch statement |static void Main(string[] args) { |
| |int n = args.Length; |
| |switch (n) { |
| |case 0: |
| |Console.WriteLine("No arguments"); |
| |break; |
| |case 1: |
| |Console.WriteLine("One argument"); |
| |break; |
| |default: |
| |Console.WriteLine("{0} arguments", n); |
| |break; |
| |} |
| |} |
| |} |
|while statement |static void Main(string[] args) { |
| |int i = 0; |
| |while (i < args.Length) { |
| |Console.WriteLine(args[i]); |
| |i++; |
| |} |
| |} |
|do statement |static void Main() { |
| |string s; |
| |do { |
| |s = Console.ReadLine(); |
| |if (s != null) Console.WriteLine(s); |
| |} while (s != null); |
| |} |
|for statement |static void Main(string[] args) { |
| |for (int i = 0; i < args.Length; i++) { |
| |Console.WriteLine(args[i]); |
| |} |
| |} |
|foreach statement |static void Main(string[] args) { |
| |foreach (string s in args) { |
| |Console.WriteLine(s); |
| |} |
| |} |
|break statement |static void Main() { |
| |while (true) { |
| |string s = Console.ReadLine(); |
| |if (s == null) break; |
| |Console.WriteLine(s); |
| |} |
| |} |
|continue statement |static void Main(string[] args) { |
| |for (int i = 0; i < args.Length; i++) { |
| |if (args[i].StartsWith("/")) continue; |
| |Console.WriteLine(args[i]); |
| |} |
| |} |

|goto statement |static void Main(string[] args) { |
| |int i = 0; |
| |goto check; |
| |loop: |
| |Console.WriteLine(args[i++]); |
| |check: |
| |if (i < args.Length) goto loop; |
| |} |
|return statement |static int Add(int a, int b) { |
| |return a + b; |
| |} |
| |static void Main() { |
| |Console.WriteLine(Add(1, 2)); |
| |return; |
| |} |
|yield statement |static IEnumerable Range(int from, int to) { |
| |for (int i = from; i < to; i++) { |
| |yield return i; |
| |} |
| |yield break; |
| |} |
| |static void Main() { |
| |foreach (int x in Range(-10,10)) { |
| |Console.WriteLine(x); |
| |} |
| |} |
|throw and try |static double Divide(double x, double y) { |
|statements |if (y == 0) throw new DivideByZeroException(); |
| |return x / y; |
| |} |
| |static void Main(string[] args) { |
| |try { |
| |if (args.Length != 2) { |
| |throw new Exception("Two numbers required"); |
| |} |
| |double x = double.Parse(args[0]); |
| |double y = double.Parse(args[1]); |
| |Console.WriteLine(Divide(x, y)); |
| |} |
| |catch (Exception e) { |
| |Console.WriteLine(e.Message); |
| |} |
| |finally { |
| |Console.WriteLine(“Good bye!”); |
| |} |
| |} |
|checked and unchecked |static void Main() { |
|statements |int i = int.MaxValue; |
| |checked { |
| |Console.WriteLine(i + 1); // Exception |
| |} |
| |unchecked { |
| |Console.WriteLine(i + 1); // Overflow |
| |} |
| |} |

|lock statement |class Account |
| |{ |
| |decimal balance; |
| |public void Withdraw(decimal amount) { |
| |lock (this) { |
| |if (amount > balance) { |
| |throw new Exception("Insufficient funds"); |
| |} |
| |balance -= amount; |
| |} |
| |} |
| |} |
|using statement |static void Main() { |
| |using (TextWriter w = File.CreateText("test.txt")) { |
| |w.WriteLine("Line one"); |
| |w.WriteLine("Line two"); |
| |w.WriteLine("Line three"); |
| |} |
| |} |

6 Classes and objects

Classes are the most fundamental of C#’s types. A class is a data structure that combines state (fields) and actions (methods and other function members) in a single unit. A class provides a definition for dynamically created instances of the class, also known as objects. Classes support inheritance and polymorphism, mechanisms whereby derived classes can extend and specialize base classes.

New classes are created using class declarations. A class declaration starts with a header that specifies the attributes and modifiers of the class, the name of the class, the base class (if given), and the interfaces implemented by the class. The header is followed by the class body, which consists of a list of member declarations written between the delimiters { and }.

The following is a declaration of a simple class named Point:

public class Point
{
public int x, y;

public Point(int x, int y) { this.x = x; this.y = y; }
}

Instances of classes are created using the new operator, which allocates memory for a new instance, invokes a constructor to initialize the instance, and returns a reference to the instance. The following statements create two Point objects and store references to those objects in two variables:

Point p1 = new Point(0, 0);
Point p2 = new Point(10, 20);

The memory occupied by an object is automatically reclaimed when the object is no longer in use. It is neither necessary nor possible to explicitly deallocate objects in C#.

1 Members

The members of a class are either static members or instance members. Static members belong to classes, and instance members belong to objects (instances of classes).

The following table provides an overview of the kinds of members a class can contain.

|Member |Description |
|Constants |Constant values associated with the class |
|Fields |Variables of the class |
|Methods |Computations and actions that can be performed by the class |
|Properties |Actions associated with reading and writing named properties of the class |
|Indexers |Actions associated with indexing instances of the class like an array |
|Events |Notifications that can be generated by the class |
|Operators |Conversions and expression operators supported by the class |
|Constructors |Actions required to initialize instances of the class or the class itself |
|Destructors |Actions to perform before instances of the class are permanently discarded |
|Types |Nested types declared by the class |

2 Accessibility

Each member of a class has an associated accessibility, which controls the regions of program text that are able to access the member. There are five possible forms of accessibility. These are summarized in the following table.

|Accessibility |Meaning |
|public |Access not limited |
|protected |Access limited to this class or classes derived from this class |
|internal |Access limited to this program |
|protected internal |Access limited to this program or classes derived from this class |
|private |Access limited to this class |

3 Type parameters

A class definition may specify a set of type parameters by following the class name with angle brackets enclosing a list of type parameter names. The type parameters can the be used in the body of the class declarations to define the members of the class. In the following example, the type parameters of Pair are TFirst and TSecond:

public class Pair
{
public TFirst First;

public TSecond Second;
}

A class type that is declared to take type parameters is called a generic class type. Struct, interface and delegate types can also be generic.

When the generic class is used, type arguments must be provided for each of the type parameters:

Pair pair = new Pair { First = 1, Second = “two” }; int i = pair.First; // TFirst is int string s = pair.Second; // TSecond is string

A generic type with type arguments provided, like Pair above, is called a constructed type.

4 Base classes

A class declaration may specify a base class by following the class name and type parameters with a colon and the name of the base class. Omitting a base class specification is the same as deriving from type object. In the following example, the base class of Point3D is Point, and the base class of Point is object:

public class Point
{
public int x, y;

public Point(int x, int y) { this.x = x; this.y = y; }
}

public class Point3D: Point
{
public int z;

public Point3D(int x, int y, int z): base(x, y) { this.z = z; }
}

A class inherits the members of its base class. Inheritance means that a class implicitly contains all members of its base class, except for the instance and static constructors, and the destructors of the base class. A derived class can add new members to those it inherits, but it cannot remove the definition of an inherited member. In the previous example, Point3D inherits the x and y fields from Point, and every Point3D instance contains three fields, x, y, and z.

An implicit conversion exists from a class type to any of its base class types. Therefore, a variable of a class type can reference an instance of that class or an instance of any derived class. For example, given the previous class declarations, a variable of type Point can reference either a Point or a Point3D:

Point a = new Point(10, 20);
Point b = new Point3D(10, 20, 30);

5 Fields

A field is a variable that is associated with a class or with an instance of a class.

A field declared with the static modifier defines a static field. A static field identifies exactly one storage location. No matter how many instances of a class are created, there is only ever one copy of a static field.

A field declared without the static modifier defines an instance field. Every instance of a class contains a separate copy of all the instance fields of that class.

In the following example, each instance of the Color class has a separate copy of the r, g, and b instance fields, but there is only one copy of the Black, White, Red, Green, and Blue static fields:

public class Color
{
public static readonly Color Black = new Color(0, 0, 0); public static readonly Color White = new Color(255, 255, 255); public static readonly Color Red = new Color(255, 0, 0); public static readonly Color Green = new Color(0, 255, 0); public static readonly Color Blue = new Color(0, 0, 255);

private byte r, g, b;

public Color(byte r, byte g, byte b) { this.r = r; this.g = g; this.b = b; }
}

As shown in the previous example, read-only fields may be declared with a readonly modifier. Assignment to a readonly field can only occur as part of the field’s declaration or in a constructor in the same class.

6 Methods

A method is a member that implements a computation or action that can be performed by an object or class. Static methods are accessed through the class. Instance methods are accessed through instances of the class.

Methods have a (possibly empty) list of parameters, which represent values or variable references passed to the method, and a return type, which specifies the type of the value computed and returned by the method. A method’s return type is void if it does not return a value.

Like types, methods may also have a set of type parameters, for which type arguments must be specified when the method is called. Unlike types, the type arguments can often be inferred from the arguments of a method call and need not be explicitly given.

The signature of a method must be unique in the class in which the method is declared. The signature of a method consists of the name of the method, the number of type parameters and the number, modifiers, and types of its parameters. The signature of a method does not include the return type.

1 Parameters

Parameters are used to pass values or variable references to methods. The parameters of a method get their actual values from the arguments that are specified when the method is invoked. There are four kinds of parameters: value parameters, reference parameters, output parameters, and parameter arrays.

A value parameter is used for input parameter passing. A value parameter corresponds to a local variable that gets its initial value from the argument that was passed for the parameter. Modifications to a value parameter do not affect the argument that was passed for the parameter.

Value parameters can be optional, by specifying a default value so that corresponding arguments can be omitted.

A reference parameter is used for both input and output parameter passing. The argument passed for a reference parameter must be a variable, and during execution of the method, the reference parameter represents the same storage location as the argument variable. A reference parameter is declared with the ref modifier. The following example shows the use of ref parameters.

using System;

class Test
{
static void Swap(ref int x, ref int y) { int temp = x; x = y; y = temp; }

static void Main() { int i = 1, j = 2; Swap(ref i, ref j); Console.WriteLine("{0} {1}", i, j); // Outputs "2 1" }
}

An output parameter is used for output parameter passing. An output parameter is similar to a reference parameter except that the initial value of the caller-provided argument is unimportant. An output parameter is declared with the out modifier. The following example shows the use of out parameters.

using System;

class Test
{
static void Divide(int x, int y, out int result, out int remainder) { result = x / y; remainder = x % y; }

static void Main() { int res, rem; Divide(10, 3, out res, out rem); Console.WriteLine("{0} {1}", res, rem); // Outputs "3 1" }
}

A parameter array permits a variable number of arguments to be passed to a method. A parameter array is declared with the params modifier. Only the last parameter of a method can be a parameter array, and the type of a parameter array must be a single-dimensional array type. The Write and WriteLine methods of the System.Console class are good examples of parameter array usage. They are declared as follows.

public class Console
{
public static void Write(string fmt, params object[] args) {...}

public static void WriteLine(string fmt, params object[] args) {...}

...
}

Within a method that uses a parameter array, the parameter array behaves exactly like a regular parameter of an array type. However, in an invocation of a method with a parameter array, it is possible to pass either a single argument of the parameter array type or any number of arguments of the element type of the parameter array. In the latter case, an array instance is automatically created and initialized with the given arguments. This example

Console.WriteLine("x={0} y={1} z={2}", x, y, z);

is equivalent to writing the following.

string s = "x={0} y={1} z={2}"; object[] args = new object[3]; args[0] = x; args[1] = y; args[2] = z;
Console.WriteLine(s, args);

2 Method body and local variables

A method’s body specifies the statements to execute when the method is invoked.

A method body can declare variables that are specific to the invocation of the method. Such variables are called local variables. A local variable declaration specifies a type name, a variable name, and possibly an initial value. The following example declares a local variable i with an initial value of zero and a local variable j with no initial value.

using System;

class Squares
{
static void Main() { int i = 0; int j; while (i < 10) { j = i * i; Console.WriteLine("{0} x {0} = {1}", i, j); i = i + 1; } }
}

C# requires a local variable to be definitely assigned before its value can be obtained. For example, if the declaration of the previous i did not include an initial value, the compiler would report an error for the subsequent usages of i because i would not be definitely assigned at those points in the program.

A method can use return statements to return control to its caller. In a method returning void, return statements cannot specify an expression. In a method returning non-void, return statements must include an expression that computes the return value.

3 Static and instance methods

A method declared with a static modifier is a static method. A static method does not operate on a specific instance and can only directly access static members.

A method declared without a static modifier is an instance method. An instance method operates on a specific instance and can access both static and instance members. The instance on which an instance method was invoked can be explicitly accessed as this. It is an error to refer to this in a static method.

The following Entity class has both static and instance members.

class Entity
{
static int nextSerialNo;

int serialNo;

public Entity() { serialNo = nextSerialNo++; }

public int GetSerialNo() { return serialNo; }

public static int GetNextSerialNo() { return nextSerialNo; }

public static void SetNextSerialNo(int value) { nextSerialNo = value; }
}

Each Entity instance contains a serial number (and presumably some other information that is not shown here). The Entity constructor (which is like an instance method) initializes the new instance with the next available serial number. Because the constructor is an instance member, it is permitted to access both the serialNo instance field and the nextSerialNo static field.

The GetNextSerialNo and SetNextSerialNo static methods can access the nextSerialNo static field, but it would be an error for them to directly access the serialNo instance field.

The following example shows the use of the Entity class.

using System;

class Test
{
static void Main() { Entity.SetNextSerialNo(1000);

Entity e1 = new Entity(); Entity e2 = new Entity();

Console.WriteLine(e1.GetSerialNo()); // Outputs "1000" Console.WriteLine(e2.GetSerialNo()); // Outputs "1001" Console.WriteLine(Entity.GetNextSerialNo()); // Outputs "1002" }
}

Note that the SetNextSerialNo and GetNextSerialNo static methods are invoked on the class whereas the GetSerialNo instance method is invoked on instances of the class.

4 Virtual, override, and abstract methods

When an instance method declaration includes a virtual modifier, the method is said to be a virtual method. When no virtual modifier is present, the method is said to be a non-virtual method.

When a virtual method is invoked, the run-time type of the instance for which that invocation takes place determines the actual method implementation to invoke. In a nonvirtual method invocation, the compile-time type of the instance is the determining factor.

A virtual method can be overridden in a derived class. When an instance method declaration includes an override modifier, the method overrides an inherited virtual method with the same signature. Whereas a virtual method declaration introduces a new method, an override method declaration specializes an existing inherited virtual method by providing a new implementation of that method.

An abstract method is a virtual method with no implementation. An abstract method is declared with the abstract modifier and is permitted only in a class that is also declared abstract. An abstract method must be overridden in every non-abstract derived class.

The following example declares an abstract class, Expression, which represents an expression tree node, and three derived classes, Constant, VariableReference, and Operation, which implement expression tree nodes for constants, variable references, and arithmetic operations. (This is similar to, but not to be confused with the expression tree types introduced in section §4.6).

using System; using System.Collections;

public abstract class Expression
{
public abstract double Evaluate(Hashtable vars);
}

public class Constant: Expression
{
double value;

public Constant(double value) { this.value = value; }

public override double Evaluate(Hashtable vars) { return value; }
}

public class VariableReference: Expression
{
string name;

public VariableReference(string name) { this.name = name; }

public override double Evaluate(Hashtable vars) { object value = vars[name]; if (value == null) { throw new Exception("Unknown variable: " + name); } return Convert.ToDouble(value); }
}

public class Operation: Expression
{
Expression left; char op; Expression right;

public Operation(Expression left, char op, Expression right) { this.left = left; this.op = op; this.right = right; }

public override double Evaluate(Hashtable vars) { double x = left.Evaluate(vars); double y = right.Evaluate(vars); switch (op) { case '+': return x + y; case '-': return x - y; case '*': return x * y; case '/': return x / y; } throw new Exception("Unknown operator"); }
}

The previous four classes can be used to model arithmetic expressions. For example, using instances of these classes, the expression x + 3 can be represented as follows.

Expression e = new Operation( new VariableReference("x"), '+', new Constant(3));

The Evaluate method of an Expression instance is invoked to evaluate the given expression and produce a double value. The method takes as an argument a Hashtable that contains variable names (as keys of the entries) and values (as values of the entries). The Evaluate method is a virtual abstract method, meaning that non-abstract derived classes must override it to provide an actual implementation.

A Constant’s implementation of Evaluate simply returns the stored constant. A VariableReference’s implementation looks up the variable name in the hashtable and returns the resulting value. An Operation’s implementation first evaluates the left and right operands (by recursively invoking their Evaluate methods) and then performs the given arithmetic operation.

The following program uses the Expression classes to evaluate the expression x * (y + 2) for different values of x and y.

using System; using System.Collections;

class Test
{
static void Main() {

Expression e = new Operation( new VariableReference("x"), '*', new Operation( new VariableReference("y"), '+', new Constant(2) ) );

Hashtable vars = new Hashtable();

vars["x"] = 3; vars["y"] = 5; Console.WriteLine(e.Evaluate(vars)); // Outputs "21"

vars["x"] = 1.5; vars["y"] = 9; Console.WriteLine(e.Evaluate(vars)); // Outputs "16.5" }
}

5 Method overloading

Method overloading permits multiple methods in the same class to have the same name as long as they have unique signatures. When compiling an invocation of an overloaded method, the compiler uses overload resolution to determine the specific method to invoke. Overload resolution finds the one method that best matches the arguments or reports an error if no single best match can be found. The following example shows overload resolution in effect. The comment for each invocation in the Main method shows which method is actually invoked.

class Test
{
static void F() { Console.WriteLine("F()"); }

static void F(object x) { Console.WriteLine("F(object)"); }

static void F(int x) { Console.WriteLine("F(int)"); }

static void F(double x) { Console.WriteLine("F(double)"); }

static void F(T x) { Console.WriteLine("F(T)"); }

static void F(double x, double y) { Console.WriteLine("F(double, double)"); }

static void Main() { F(); // Invokes F() F(1); // Invokes F(int) F(1.0); // Invokes F(double) F("abc"); // Invokes F(object) F((double)1); // Invokes F(double) F((object)1); // Invokes F(object) F(1); // Invokes F(T) F(1, 1); // Invokes F(double, double) }
}

As shown by the example, a particular method can always be selected by explicitly casting the arguments to the exact parameter types and/or explicitly supplying type arguments.

7 Other function members

Members that contain executable code are collectively known as the function members of a class. The preceding section describes methods, which are the primary kind of function members. This section describes the other kinds of function members supported by C#: constructors, properties, indexers, events, operators, and destructors.

The following table shows a generic class called List, which implements a growable list of objects. The class contains several examples of the most common kinds of function members.

|public class List |
|{ |
| const int defaultCapacity = 4; |Constant |
| T[] items; |Fields |
|int count; | |
| public List(int capacity = defaultCapacity) { |Constructors |
|items = new T[capacity]; | |
|} | |
| public int Count { |Properties |
|get { return count; } | |
|} | |
|public int Capacity { | |
|get { | |
|return items.Length; | |
|} | |
|set { | |
|if (value < count) value = count; | |
|if (value != items.Length) { | |
|T[] newItems = new T[value]; | |
|Array.Copy(items, 0, newItems, 0, count); | |
|items = newItems; | |
|} | |
|} | |
|} | |

| public T this[int index] { |Indexer |
|get { | |
|return items[index]; | |
|} | |
|set { | |
|items[index] = value; | |
|OnChanged(); | |
|} | |
|} | |
| public void Add(T item) { |Methods |
|if (count == Capacity) Capacity = count * 2; | |
|items[count] = item; | |
|count++; | |
|OnChanged(); | |
|} | |
|protected virtual void OnChanged() { | |
|if (Changed != null) Changed(this, EventArgs.Empty); | |
|} | |
|public override bool Equals(object other) { | |
|return Equals(this, other as List); | |
|} | |
|static bool Equals(List a, List b) { | |
|if (a == null) return b == null; | |
|if (b == null || a.count != b.count) return false; | |
|for (int i = 0; i < a.count; i++) { | |
|if (!object.Equals(a.items[i], b.items[i])) { | |
|return false; | |
|} | |
|} | |
|return true; | |
|} | |
| public event EventHandler Changed; |Event |
| public static bool operator ==(List a, List b) { |Operators |
|return Equals(a, b); | |
|} | |
|public static bool operator !=(List a, List b) { | |
|return !Equals(a, b); | |
|} | |
|} |

1 Constructors

C# supports both instance and static constructors. An instance constructor is a member that implements the actions required to initialize an instance of a class. A static constructor is a member that implements the actions required to initialize a class itself when it is first loaded.

A constructor is declared like a method with no return type and the same name as the containing class. If a constructor declaration includes a static modifier, it declares a static constructor. Otherwise, it declares an instance constructor.

Instance constructors can be overloaded. For example, the List class declares two instance constructors, one with no parameters and one that takes an int parameter. Instance constructors are invoked using the new operator. The following statements allocate two List instances using each of the constructors of the List class.

List list1 = new List();
List list2 = new List(10);

Unlike other members, instance constructors are not inherited, and a class has no instance constructors other than those actually declared in the class. If no instance constructor is supplied for a class, then an empty one with no parameters is automatically provided.

2 Properties

Properties are a natural extension of fields. Both are named members with associated types, and the syntax for accessing fields and properties is the same. However, unlike fields, properties do not denote storage locations. Instead, properties have accessors that specify the statements to be executed when their values are read or written.

A property is declared like a field, except that the declaration ends with a get accessor and/or a set accessor written between the delimiters { and } instead of ending in a semicolon. A property that has both a get accessor and a set accessor is a read-write property, a property that has only a get accessor is a read-only property, and a property that has only a set accessor is a write-only property.

A get accessor corresponds to a parameterless method with a return value of the property type. Except as the target of an assignment, when a property is referenced in an expression, the get accessor of the property is invoked to compute the value of the property.

A set accessor corresponds to a method with a single parameter named value and no return type. When a property is referenced as the target of an assignment or as the operand of ++ or --, the set accessor is invoked with an argument that provides the new value.

The List class declares two properties, Count and Capacity, which are read-only and read-write, respectively. The following is an example of use of these properties.

List names = new List(); names.Capacity = 100; // Invokes set accessor int i = names.Count; // Invokes get accessor int j = names.Capacity; // Invokes get accessor

Similar to fields and methods, C# supports both instance properties and static properties. Static properties are declared with the static modifier, and instance properties are declared without it.

The accessor(s) of a property can be virtual. When a property declaration includes a virtual, abstract, or override modifier, it applies to the accessor(s) of the property.

3 Indexers

An indexer is a member that enables objects to be indexed in the same way as an array. An indexer is declared like a property except that the name of the member is this followed by a parameter list written between the delimiters [ and ]. The parameters are available in the accessor(s) of the indexer. Similar to properties, indexers can be read-write, read-only, and write-only, and the accessor(s) of an indexer can be virtual.

The List class declares a single read-write indexer that takes an int parameter. The indexer makes it possible to index List instances with int values. For example

List names = new List(); names.Add("Liz"); names.Add("Martha"); names.Add("Beth"); for (int i = 0; i < names.Count; i++) { string s = names[i]; names[i] = s.ToUpper();
}

Indexers can be overloaded, meaning that a class can declare multiple indexers as long as the number or types of their parameters differ.

4 Events

An event is a member that enables a class or object to provide notifications. An event is declared like a field except that the declaration includes an event keyword and the type must be a delegate type.

Within a class that declares an event member, the event behaves just like a field of a delegate type (provided the event is not abstract and does not declare accessors). The field stores a reference to a delegate that represents the event handlers that have been added to the event. If no event handles are present, the field is null.

The List class declares a single event member called Changed, which indicates that a new item has been added to the list. The Changed event is raised by the OnChanged virtual method, which first checks whether the event is null (meaning that no handlers are present). The notion of raising an event is precisely equivalent to invoking the delegate represented by the event—thus, there are no special language constructs for raising events.

Clients react to events through event handlers. Event handlers are attached using the += operator and removed using the -= operator. The following example attaches an event handler to the Changed event of a List.

using System;

class Test
{
static int changeCount;

static void ListChanged(object sender, EventArgs e) { changeCount++; }

static void Main() { List names = new List(); names.Changed += new EventHandler(ListChanged); names.Add("Liz"); names.Add("Martha"); names.Add("Beth"); Console.WriteLine(changeCount); // Outputs "3" }
}

For advanced scenarios where control of the underlying storage of an event is desired, an event declaration can explicitly provide add and remove accessors, which are somewhat similar to the set accessor of a property.

5 Operators

An operator is a member that defines the meaning of applying a particular expression operator to instances of a class. Three kinds of operators can be defined: unary operators, binary operators, and conversion operators. All operators must be declared as public and static.

The List class declares two operators, operator == and operator !=, and thus gives new meaning to expressions that apply those operators to List instances. Specifically, the operators define equality of two List instances as comparing each of the contained objects using their Equals methods. The following example uses the == operator to compare two List instances.

using System;

class Test
{
static void Main() { List a = new List(); a.Add(1); a.Add(2); List b = new List(); b.Add(1); b.Add(2); Console.WriteLine(a == b); // Outputs "True" b.Add(3); Console.WriteLine(a == b); // Outputs "False" }
}

The first Console.WriteLine outputs True because the two lists contain the same number of objects with the same values in the same order. Had List not defined operator ==, the first Console.WriteLine would have output False because a and b reference different List instances.

6 Destructors

A destructor is a member that implements the actions required to destruct an instance of a class. Destructors cannot have parameters, they cannot have accessibility modifiers, and they cannot be invoked explicitly. The destructor for an instance is invoked automatically during garbage collection.

The garbage collector is allowed wide latitude in deciding when to collect objects and run destructors. Specifically, the timing of destructor invocations is not deterministic, and destructors may be executed on any thread. For these and other reasons, classes should implement destructors only when no other solutions are feasible.

The using statement provides a better approach to object destruction.

7 Structs

Like classes, structs are data structures that can contain data members and function members, but unlike classes, structs are value types and do not require heap allocation. A variable of a struct type directly stores the data of the struct, whereas a variable of a class type stores a reference to a dynamically allocated object. Struct types do not support user-specified inheritance, and all struct types implicitly inherit from type object.

Structs are particularly useful for small data structures that have value semantics. Complex numbers, points in a coordinate system, or key-value pairs in a dictionary are all good examples of structs. The use of structs rather than classes for small data structures can make a large difference in the number of memory allocations an application performs. For example, the following program creates and initializes an array of 100 points. With Point implemented as a class, 101 separate objects are instantiated—one for the array and one each for the 100 elements.

class Point
{
public int x, y;

public Point(int x, int y) { this.x = x; this.y = y; }
}

class Test
{
static void Main() { Point[] points = new Point[100]; for (int i = 0; i < 100; i++) points[i] = new Point(i, i); }
}

An alternative is to make Point a struct.

struct Point
{
public int x, y;

public Point(int x, int y) { this.x = x; this.y = y; }
}

Now, only one object is instantiated—the one for the array—and the Point instances are stored in-line in the array.

Struct constructors are invoked with the new operator, but that does not imply that memory is being allocated. Instead of dynamically allocating an object and returning a reference to it, a struct constructor simply returns the struct value itself (typically in a temporary location on the stack), and this value is then copied as necessary.

With classes, it is possible for two variables to reference the same object and thus possible for operations on one variable to affect the object referenced by the other variable. With structs, the variables each have their own copy of the data, and it is not possible for operations on one to affect the other. For example, the output produced by the following code fragment depends on whether Point is a class or a struct.

Point a = new Point(10, 10);
Point b = a;
a.x = 20;
Console.WriteLine(b.x);

If Point is a class, the output is 20 because a and b reference the same object. If Point is a struct, the output is 10 because the assignment of a to b creates a copy of the value, and this copy is unaffected by the subsequent assignment to a.x.

The previous example highlights two of the limitations of structs. First, copying an entire struct is typically less efficient than copying an object reference, so assignment and value parameter passing can be more expensive with structs than with reference types. Second, except for ref and out parameters, it is not possible to create references to structs, which rules out their usage in a number of situations.

8 Arrays

An array is a data structure that contains a number of variables that are accessed through computed indices. The variables contained in an array, also called the elements of the array, are all of the same type, and this type is called the element type of the array.

Array types are reference types, and the declaration of an array variable simply sets aside space for a reference to an array instance. Actual array instances are created dynamically at run-time using the new operator. The new operation specifies the length of the new array instance, which is then fixed for the lifetime of the instance. The indices of the elements of an array range from 0 to Length - 1. The new operator automatically initializes the elements of an array to their default value, which, for example, is zero for all numeric types and null for all reference types.

The following example creates an array of int elements, initializes the array, and prints out the contents of the array.

using System;

class Test
{
static void Main() { int[] a = new int[10]; for (int i = 0; i < a.Length; i++) { a[i] = i * i; } for (int i = 0; i < a.Length; i++) { Console.WriteLine("a[{0}] = {1}", i, a[i]); } }
}

This example creates and operates on a single-dimensional array. C# also supports multi-dimensional arrays. The number of dimensions of an array type, also known as the rank of the array type, is one plus the number of commas written between the square brackets of the array type. The following example allocates a one-dimensional, a two-dimensional, and a three-dimensional array.

int[] a1 = new int[10]; int[,] a2 = new int[10, 5]; int[,,] a3 = new int[10, 5, 2];

The a1 array contains 10 elements, the a2 array contains 50 (10 × 5) elements, and the a3 array contains 100 (10 × 5 × 2) elements.

The element type of an array can be any type, including an array type. An array with elements of an array type is sometimes called a jagged array because the lengths of the element arrays do not all have to be the same. The following example allocates an array of arrays of int:

int[][] a = new int[3][]; a[0] = new int[10]; a[1] = new int[5]; a[2] = new int[20];

The first line creates an array with three elements, each of type int[] and each with an initial value of null. The subsequent lines then initialize the three elements with references to individual array instances of varying lengths.

The new operator permits the initial values of the array elements to be specified using an array initializer, which is a list of expressions written between the delimiters { and }. The following example allocates and initializes an int[] with three elements.

int[] a = new int[] {1, 2, 3};

Note that the length of the array is inferred from the number of expressions between { and }. Local variable and field declarations can be shortened further such that the array type does not have to be restated.

int[] a = {1, 2, 3};

Both of the previous examples are equivalent to the following:

int[] t = new int[3]; t[0] = 1; t[1] = 2; t[2] = 3; int[] a = t;

9 Interfaces

An interface defines a contract that can be implemented by classes and structs. An interface can contain methods, properties, events, and indexers. An interface does not provide implementations of the members it defines—it merely specifies the members that must be supplied by classes or structs that implement the interface.

Interfaces may employ multiple inheritance. In the following example, the interface IComboBox inherits from both ITextBox and IListBox.

interface IControl
{
void Paint();
}

interface ITextBox: IControl
{
void SetText(string text);
}

interface IListBox: IControl
{
void SetItems(string[] items);
}

interface IComboBox: ITextBox, IListBox {}

Classes and structs can implement multiple interfaces. In the following example, the class EditBox implements both IControl and IDataBound.

interface IDataBound
{
void Bind(Binder b);
}

public class EditBox: IControl, IDataBound
{
public void Paint() {...}

public void Bind(Binder b) {...}
}

When a class or struct implements a particular interface, instances of that class or struct can be implicitly converted to that interface type. For example

EditBox editBox = new EditBox();
IControl control = editBox;
IDataBound dataBound = editBox;

In cases where an instance is not statically known to implement a particular interface, dynamic type casts can be used. For example, the following statements use dynamic type casts to obtain an object’s IControl and IDataBound interface implementations. Because the actual type of the object is EditBox, the casts succeed.

object obj = new EditBox();
IControl control = (IControl)obj;
IDataBound dataBound = (IDataBound)obj;

In the previous EditBox class, the Paint method from the IControl interface and the Bind method from the IDataBound interface are implemented using public members. C# also supports explicit interface member implementations, using which the class or struct can avoid making the members public. An explicit interface member implementation is written using the fully qualified interface member name. For example, the EditBox class could implement the IControl.Paint and IDataBound.Bind methods using explicit interface member implementations as follows.

public class EditBox: IControl, IDataBound
{
void IControl.Paint() {...}

void IDataBound.Bind(Binder b) {...}
}

Explicit interface members can only be accessed via the interface type. For example, the implementation of IControl.Paint provided by the previous EditBox class can only be invoked by first converting the EditBox reference to the IControl interface type.

EditBox editBox = new EditBox(); editBox.Paint(); // Error, no such method
IControl control = editBox; control.Paint(); // Ok

10 Enums

An enum type is a distinct value type with a set of named constants. The following example declares and uses an enum type named Color with three constant values, Red, Green, and Blue.

using System;

enum Color
{
Red, Green, Blue
}

class Test
{
static void PrintColor(Color color) { switch (color) { case Color.Red: Console.WriteLine("Red"); break; case Color.Green: Console.WriteLine("Green"); break; case Color.Blue: Console.WriteLine("Blue"); break; default: Console.WriteLine("Unknown color"); break; } }

static void Main() { Color c = Color.Red; PrintColor(c); PrintColor(Color.Blue); }
}

Each enum type has a corresponding integral type called the underlying type of the enum type. An enum type that does not explicitly declare an underlying type has an underlying type of int. An enum type’s storage format and range of possible values are determined by its underlying type. The set of values that an enum type can take on is not limited by its enum members. In particular, any value of the underlying type of an enum can be cast to the enum type and is a distinct valid value of that enum type.

The following example declares an enum type named Alignment with an underlying type of sbyte.

enum Alignment: sbyte
{
Left = -1, Center = 0, Right = 1
}

As shown by the previous example, an enum member declaration can include a constant expression that specifies the value of the member. The constant value for each enum member must be in the range of the underlying type of the enum. When an enum member declaration does not explicitly specify a value, the member is given the value zero (if it is the first member in the enum type) or the value of the textually preceding enum member plus one.

Enum values can be converted to integral values and vice versa using type casts. For example

int i = (int)Color.Blue; // int i = 2;
Color c = (Color)2; // Color c = Color.Blue;

The default value of any enum type is the integral value zero converted to the enum type. In cases where variables are automatically initialized to a default value, this is the value given to variables of enum types. In order for the default value of an enum type to be easily available, the literal 0 implicitly converts to any enum type. Thus, the following is permitted.

Color c = 0;

11 Delegates

A delegate type represents references to methods with a particular parameter list and return type. Delegates make it possible to treat methods as entities that can be assigned to variables and passed as parameters. Delegates are similar to the concept of function pointers found in some other languages, but unlike function pointers, delegates are object-oriented and type-safe.

The following example declares and uses a delegate type named Function.

using System;

delegate double Function(double x);

class Multiplier
{
double factor;

public Multiplier(double factor) { this.factor = factor; }

public double Multiply(double x) { return x * factor; }
}

class Test
{
static double Square(double x) { return x * x; }

static double[] Apply(double[] a, Function f) { double[] result = new double[a.Length]; for (int i = 0; i < a.Length; i++) result[i] = f(a[i]); return result; }

static void Main() { double[] a = {0.0, 0.5, 1.0};

double[] squares = Apply(a, Square);

double[] sines = Apply(a, Math.Sin);

Multiplier m = new Multiplier(2.0); double[] doubles = Apply(a, m.Multiply); }
}

An instance of the Function delegate type can reference any method that takes a double argument and returns a double value. The Apply method applies a given Function to the elements of a double[], returning a double[] with the results. In the Main method, Apply is used to apply three different functions to a double[].

A delegate can reference either a static method (such as Square or Math.Sin in the previous example) or an instance method (such as m.Multiply in the previous example). A delegate that references an instance method also references a particular object, and when the instance method is invoked through the delegate, that object becomes this in the invocation.

Delegates can also be created using anonymous functions, which are “inline methods” that are created on the fly. Anonymous functions can see the local variables of the sourrounding methods. Thus, the multiplier example above can be written more easily without using a Multiplier class:

double[] doubles = Apply(a, (double x) => x * 2.0);

An interesting and useful property of a delegate is that it does not know or care about the class of the method it references; all that matters is that the referenced method has the same parameters and return type as the delegate.

12 Attributes

Types, members, and other entities in a C# program support modifiers that control certain aspects of their behavior. For example, the accessibility of a method is controlled using the public, protected, internal, and private modifiers. C# generalizes this capability such that user-defined types of declarative information can be attached to program entities and retrieved at run-time. Programs specify this additional declarative information by defining and using attributes.

The following example declares a HelpAttribute attribute that can be placed on program entities to provide links to their associated documentation.

using System;

public class HelpAttribute: Attribute
{
string url; string topic;

public HelpAttribute(string url) { this.url = url; }

public string Url { get { return url; } }

public string Topic { get { return topic; } set { topic = value; } }
}

All attribute classes derive from the System.Attribute base class provided by the .NET Framework. Attributes can be applied by giving their name, along with any arguments, inside square brackets just before the associated declaration. If an attribute’s name ends in Attribute, that part of the name can be omitted when the attribute is referenced. For example, the HelpAttribute attribute can be used as follows.

[Help("http://msdn.microsoft.com/.../MyClass.htm")] public class Widget
{
[Help("http://msdn.microsoft.com/.../MyClass.htm", Topic = "Display")] public void Display(string text) {}
}

This example attaches a HelpAttribute to the Widget class and another HelpAttribute to the Display method in the class. The public constructors of an attribute class control the information that must be provided when the attribute is attached to a program entity. Additional information can be provided by referencing public read-write properties of the attribute class (such as the reference to the Topic property previously).

The following example shows how attribute information for a given program entity can be retrieved at run-time using reflection.

using System; using System.Reflection;

class Test
{
static void ShowHelp(MemberInfo member) { HelpAttribute a = Attribute.GetCustomAttribute(member, typeof(HelpAttribute)) as HelpAttribute; if (a == null) { Console.WriteLine("No help for {0}", member); } else { Console.WriteLine("Help for {0}:", member); Console.WriteLine(" Url={0}, Topic={1}", a.Url, a.Topic); } }

static void Main() { ShowHelp(typeof(Widget)); ShowHelp(typeof(Widget).GetMethod("Display")); }
}

When a particular attribute is requested through reflection, the constructor for the attribute class is invoked with the information provided in the program source, and the resulting attribute instance is returned. If additional information was provided through properties, those properties are set to the given values before the attribute instance is returned.

Lexical structure

1 Programs

A C# program consists of one or more source files, known formally as compilation units (§9.1). A source file is an ordered sequence of Unicode characters. Source files typically have a one-to-one correspondence with files in a file system, but this correspondence is not required. For maximal portability, it is recommended that files in a file system be encoded with the UTF-8 encoding.

Conceptually speaking, a program is compiled using three steps:

Transformation, which converts a file from a particular character repertoire and encoding scheme into a sequence of Unicode characters.

Lexical analysis, which translates a stream of Unicode input characters into a stream of tokens.

Syntactic analysis, which translates the stream of tokens into executable code.

2 Grammars

This specification presents the syntax of the C# programming language using two grammars. The lexical grammar (§2.2.2) defines how Unicode characters are combined to form line terminators, white space, comments, tokens, and pre-processing directives. The syntactic grammar (§2.2.3) defines how the tokens resulting from the lexical grammar are combined to form C# programs.

1 Grammar notation

The lexical and syntactic grammars are presented using grammar productions. Each grammar production defines a non-terminal symbol and the possible expansions of that non-terminal symbol into sequences of non-terminal or terminal symbols. In grammar productions, non-terminal symbols are shown in italic type, and terminal symbols are shown in a fixed-width font.

The first line of a grammar production is the name of the non-terminal symbol being defined, followed by a colon. Each successive indented line contains a possible expansion of the non-terminal given as a sequence of non-terminal or terminal symbols. For example, the production:

while-statement: while ( boolean-expression ) embedded-statement

defines a while-statement to consist of the token while, followed by the token “(”, followed by a boolean-expression, followed by the token “)”, followed by an embedded-statement.

When there is more than one possible expansion of a non-terminal symbol, the alternatives are listed on separate lines. For example, the production:

statement-list: statement statement-list statement

defines a statement-list to either consist of a statement or consist of a statement-list followed by a statement. In other words, the definition is recursive and specifies that a statement list consists of one or more statements.

A subscripted suffix “opt” is used to indicate an optional symbol. The production:

block:
{ statement-listopt }

is shorthand for:

block:
{ }
{ statement-list }

and defines a block to consist of an optional statement-list enclosed in “{” and “}” tokens.

Alternatives are normally listed on separate lines, though in cases where there are many alternatives, the phrase “one of” may precede a list of expansions given on a single line. This is simply shorthand for listing each of the alternatives on a separate line. For example, the production:

real-type-suffix: one of
F f D d M m

is shorthand for:

real-type-suffix:
F
f
D
d
M
m

2 Lexical grammar

The lexical grammar of C# is presented in §2.3, §2.4, and §2.5. The terminal symbols of the lexical grammar are the characters of the Unicode character set, and the lexical grammar specifies how characters are combined to form tokens (§2.4), white space (§2.3.3), comments (§2.3.2), and pre-processing directives (§2.5).

Every source file in a C# program must conform to the input production of the lexical grammar (§2.3).

3 Syntactic grammar

The syntactic grammar of C# is presented in the chapters and appendices that follow this chapter. The terminal symbols of the syntactic grammar are the tokens defined by the lexical grammar, and the syntactic grammar specifies how tokens are combined to form C# programs.

Every source file in a C# program must conform to the compilation-unit production of the syntactic grammar (§9.1).

3 Lexical analysis

The input production defines the lexical structure of a C# source file. Each source file in a C# program must conform to this lexical grammar production.

input: input-sectionopt input-section: input-section-part input-section input-section-part

input-section-part: input-elementsopt new-line pp-directive input-elements: input-element input-elements input-element

input-element: whitespace comment token Five basic elements make up the lexical structure of a C# source file: Line terminators (§2.3.1), white space (§2.3.3), comments (§2.3.2), tokens (§2.4), and pre-processing directives (§2.5). Of these basic elements, only tokens are significant in the syntactic grammar of a C# program (§2.2.3).

The lexical processing of a C# source file consists of reducing the file into a sequence of tokens which becomes the input to the syntactic analysis. Line terminators, white space, and comments can serve to separate tokens, and pre-processing directives can cause sections of the source file to be skipped, but otherwise these lexical elements have no impact on the syntactic structure of a C# program.

When several lexical grammar productions match a sequence of characters in a source file, the lexical processing always forms the longest possible lexical element. For example, the character sequence // is processed as the beginning of a single-line comment because that lexical element is longer than a single / token.

1 Line terminators

Line terminators divide the characters of a C# source file into lines.

new-line:
Carriage return character (U+000D)
Line feed character (U+000A)
Carriage return character (U+000D) followed by line feed character (U+000A)
Next line character (U+0085)
Line separator character (U+2028)
Paragraph separator character (U+2029)

For compatibility with source code editing tools that add end-of-file markers, and to enable a source file to be viewed as a sequence of properly terminated lines, the following transformations are applied, in order, to every source file in a C# program:

If the last character of the source file is a Control-Z character (U+001A), this character is deleted.

A carriage-return character (U+000D) is added to the end of the source file if that source file is non-empty and if the last character of the source file is not a carriage return (U+000D), a line feed (U+000A), a line separator (U+2028), or a paragraph separator (U+2029).

2 Comments

Two forms of comments are supported: single-line comments and delimited comments. Single-line comments start with the characters // and extend to the end of the source line. Delimited comments start with the characters /* and end with the characters */. Delimited comments may span multiple lines.

comment: single-line-comment delimited-comment

single-line-comment:
// input-charactersopt

input-characters: input-character input-characters input-character

input-character:
Any Unicode character except a new-line-character

new-line-character:
Carriage return character (U+000D)
Line feed character (U+000A)
Next line character (U+0085)
Line separator character (U+2028)
Paragraph separator character (U+2029)

delimited-comment:
/* delimited-comment-textopt asterisks /

delimited-comment-text: delimited-comment-section delimited-comment-text delimited-comment-section

delimited-comment-section:
/
asterisksopt not-slash-or-asterisk

asterisks:
*
asterisks *

not-slash-or-asterisk:
Any Unicode character except / or *

Comments do not nest. The character sequences /* and */ have no special meaning within a // comment, and the character sequences // and /* have no special meaning within a delimited comment.

Comments are not processed within character and string literals.

The example

/* Hello, world program This program writes “hello, world” to the console
*/
class Hello
{
static void Main() { System.Console.WriteLine("hello, world"); }
}

includes a delimited comment.

The example

// Hello, world program
// This program writes “hello, world” to the console
//
class Hello // any name will do for this class
{
static void Main() { // this method must be named "Main" System.Console.WriteLine("hello, world"); }
}

shows several single-line comments.

3 White space

White space is defined as any character with Unicode class Zs (which includes the space character) as well as the horizontal tab character, the vertical tab character, and the form feed character.

whitespace:
Any character with Unicode class Zs
Horizontal tab character (U+0009)
Vertical tab character (U+000B)
Form feed character (U+000C)

4 Tokens

There are several kinds of tokens: identifiers, keywords, literals, operators, and punctuators. White space and comments are not tokens, though they act as separators for tokens.

token: identifier keyword integer-literal real-literal character-literal string-literal operator-or-punctuator 1 Unicode character escape sequences

A Unicode character escape sequence represents a Unicode character. Unicode character escape sequences are processed in identifiers (§2.4.2), character literals (§2.4.4.4), and regular string literals (§2.4.4.5). A Unicode character escape is not processed in any other location (for example, to form an operator, punctuator, or keyword).

unicode-escape-sequence:
\u hex-digit hex-digit hex-digit hex-digit
\U hex-digit hex-digit hex-digit hex-digit hex-digit hex-digit hex-digit hex-digit

A Unicode escape sequence represents the single Unicode character formed by the hexadecimal number following the “\u” or “\U” characters. Since C# uses a 16-bit encoding of Unicode code points in characters and string values, a Unicode character in the range U+10000 to U+10FFFF is not permitted in a character literal and is represented using a Unicode surrogate pair in a string literal. Unicode characters with code points above 0x10FFFF are not supported.

Multiple translations are not performed. For instance, the string literal “\u005Cu005C” is equivalent to “\u005C” rather than “\”. The Unicode value \u005C is the character “\”.

The example

class Class1
{
static void Test(bool \u0066) { char c = '\u0066'; if (\u0066) System.Console.WriteLine(c.ToString()); }
}

shows several uses of \u0066, which is the escape sequence for the letter “f”. The program is equivalent to

class Class1
{
static void Test(bool f) { char c = 'f'; if (f) System.Console.WriteLine(c.ToString()); }
}

2 Identifiers

The rules for identifiers given in this section correspond exactly to those recommended by the Unicode Standard Annex 31, except that underscore is allowed as an initial character (as is traditional in the C programming language), Unicode escape sequences are permitted in identifiers, and the “@” character is allowed as a prefix to enable keywords to be used as identifiers.

identifier: available-identifier @ identifier-or-keyword

available-identifier:
An identifier-or-keyword that is not a keyword

identifier-or-keyword: identifier-start-character identifier-part-charactersopt

identifier-start-character: letter-character _ (the underscore character U+005F)

identifier-part-characters: identifier-part-character identifier-part-characters identifier-part-character

identifier-part-character: letter-character decimal-digit-character connecting-character combining-character formatting-character letter-character:
A Unicode character of classes Lu, Ll, Lt, Lm, Lo, or Nl
A unicode-escape-sequence representing a character of classes Lu, Ll, Lt, Lm, Lo, or Nl

combining-character:
A Unicode character of classes Mn or Mc
A unicode-escape-sequence representing a character of classes Mn or Mc

decimal-digit-character:
A Unicode character of the class Nd
A unicode-escape-sequence representing a character of the class Nd

connecting-character:
A Unicode character of the class Pc
A unicode-escape-sequence representing a character of the class Pc

formatting-character:
A Unicode character of the class Cf
A unicode-escape-sequence representing a character of the class Cf

For information on the Unicode character classes mentioned above, see The Unicode Standard, Version 3.0, section 4.5.

Examples of valid identifiers include “identifier1”, “_identifier2”, and “@if”.

An identifier in a conforming program must be in the canonical format defined by Unicode Normalization Form C, as defined by Unicode Standard Annex 15. The behavior when encountering an identifier not in Normalization Form C is implementation-defined; however, a diagnostic is not required.

The prefix “@” enables the use of keywords as identifiers, which is useful when interfacing with other programming languages. The character @ is not actually part of the identifier, so the identifier might be seen in other languages as a normal identifier, without the prefix. An identifier with an @ prefix is called a verbatim identifier. Use of the @ prefix for identifiers that are not keywords is permitted, but strongly discouraged as a matter of style.

The example:

class @class
{
public static void @static(bool @bool) { if (@bool) System.Console.WriteLine("true"); else System.Console.WriteLine("false"); }
}

class Class1
{
static void M() { cl\u0061ss.st\u0061tic(true); }
}

defines a class named “class” with a static method named “static” that takes a parameter named “bool”. Note that since Unicode escapes are not permitted in keywords, the token “cl\u0061ss” is an identifier, and is the same identifier as “@class”.

Two identifiers are considered the same if they are identical after the following transformations are applied, in order:

The prefix “@”, if used, is removed.

Each unicode-escape-sequence is transformed into its corresponding Unicode character.

Any formatting-characters are removed.

Identifiers containing two consecutive underscore characters (U+005F) are reserved for use by the implementation. For example, an implementation might provide extended keywords that begin with two underscores.

3 Keywords

A keyword is an identifier-like sequence of characters that is reserved, and cannot be used as an identifier except when prefaced by the @ character.

keyword: one of abstract as base bool break byte case catch char checked class const continue decimal default delegate do double else enum event explicit extern false finally fixed float for foreach goto if implicit in int interface internal is lock long namespace new null object operator out override params private protected public readonly ref return sbyte sealed short sizeof stackalloc static string struct switch this throw true try typeof uint ulong unchecked unsafe ushort using virtual void volatile while

In some places in the grammar, specific identifiers have special meaning, but are not keywords. Such identifiers are sometimes referred to as “contextual keywords”. For example, within a property declaration, the “get” and “set” identifiers have special meaning (§10.7.2). An identifier other than get or set is never permitted in these locations, so this use does not conflict with a use of these words as identifiers. In other cases, such as with the identifier “var” in implicitly typed local variable declarations (§8.5.1), a contectual keyword can conflict with declared names. In such cases, the declared name takes precedence over the use of the identifier as a contextual keyword.

4 Literals

A literal is a source code representation of a value.

literal: boolean-literal integer-literal real-literal character-literal string-literal null-literal

1 Boolean literals

There are two boolean literal values: true and false.

boolean-literal: true false

The type of a boolean-literal is bool.

2 Integer literals

Integer literals are used to write values of types int, uint, long, and ulong. Integer literals have two possible forms: decimal and hexadecimal.

integer-literal: decimal-integer-literal hexadecimal-integer-literal

decimal-integer-literal: decimal-digits integer-type-suffixopt

decimal-digits: decimal-digit decimal-digits decimal-digit

decimal-digit: one of
0 1 2 3 4 5 6 7 8 9

integer-type-suffix: one of
U u L l UL Ul uL ul LU Lu lU lu

hexadecimal-integer-literal:
0x hex-digits integer-type-suffixopt
0X hex-digits integer-type-suffixopt

hex-digits: hex-digit hex-digits hex-digit

hex-digit: one of
0 1 2 3 4 5 6 7 8 9 A B C D E F a b c d e f

The type of an integer literal is determined as follows:

If the literal has no suffix, it has the first of these types in which its value can be represented: int, uint, long, ulong.

If the literal is suffixed by U or u, it has the first of these types in which its value can be represented: uint, ulong.

If the literal is suffixed by L or l, it has the first of these types in which its value can be represented: long, ulong.

If the literal is suffixed by UL, Ul, uL, ul, LU, Lu, lU, or lu, it is of type ulong.

If the value represented by an integer literal is outside the range of the ulong type, a compile-time error occurs.

As a matter of style, it is suggested that “L” be used instead of “l” when writing literals of type long, since it is easy to confuse the letter “l” with the digit “1”.

To permit the smallest possible int and long values to be written as decimal integer literals, the following two rules exist:

When a decimal-integer-literal with the value 2147483648 (231) and no integer-type-suffix appears as the token immediately following a unary minus operator token (§7.7.2), the result is a constant of type int with the value −2147483648 (−231). In all other situations, such a decimal-integer-literal is of type uint.

When a decimal-integer-literal with the value 9223372036854775808 (263) and no integer-type-suffix or the integer-type-suffix L or l appears as the token immediately following a unary minus operator token (§7.7.2), the result is a constant of type long with the value −9223372036854775808 (−263). In all other situations, such a decimal-integer-literal is of type ulong.

3 Real literals

Real literals are used to write values of types float, double, and decimal.

real-literal: decimal-digits . decimal-digits exponent-partopt real-type-suffixopt
. decimal-digits exponent-partopt real-type-suffixopt decimal-digits exponent-part real-type-suffixopt decimal-digits real-type-suffix

exponent-part: e signopt decimal-digits
E signopt decimal-digits

sign: one of
+ -

real-type-suffix: one of
F f D d M m

If no real-type-suffix is specified, the type of the real literal is double. Otherwise, the real type suffix determines the type of the real literal, as follows:

A real literal suffixed by F or f is of type float. For example, the literals 1f, 1.5f, 1e10f, and 123.456F are all of type float.

A real literal suffixed by D or d is of type double. For example, the literals 1d, 1.5d, 1e10d, and 123.456D are all of type double.

A real literal suffixed by M or m is of type decimal. For example, the literals 1m, 1.5m, 1e10m, and 123.456M are all of type decimal. This literal is converted to a decimal value by taking the exact value, and, if necessary, rounding to the nearest representable value using banker's rounding (§4.1.7). Any scale apparent in the literal is preserved unless the value is rounded or the value is zero (in which latter case the sign and scale will be 0). Hence, the literal 2.900m will be parsed to form the decimal with sign 0, coefficient 2900, and scale 3.

If the specified literal cannot be represented in the indicated type, a compile-time error occurs.

The value of a real literal of type float or double is determined by using the IEEE “round to nearest” mode.

Note that in a real literal, decimal digits are always required after the decimal point. For example, 1.3F is a real literal but 1.F is not.

4 Character literals

A character literal represents a single character, and usually consists of a character in quotes, as in 'a'.

character-literal:
' character '

character: single-character simple-escape-sequence hexadecimal-escape-sequence unicode-escape-sequence

single-character: Any character except ' (U+0027), \ (U+005C), and new-line-character

simple-escape-sequence: one of
\' \" \\ \0 \a \b \f \n \r \t \v

hexadecimal-escape-sequence:
\x hex-digit hex-digitopt hex-digitopt hex-digitopt

A character that follows a backslash character (\) in a character must be one of the following characters: ', ", \, 0, a, b, f, n, r, t, u, U, x, v. Otherwise, a compile-time error occurs.

A hexadecimal escape sequence represents a single Unicode character, with the value formed by the hexadecimal number following “\x”.

If the value represented by a character literal is greater than U+FFFF, a compile-time error occurs.

A Unicode character escape sequence (§2.4.1) in a character literal must be in the range U+0000 to U+FFFF.

A simple escape sequence represents a Unicode character encoding, as described in the table below.

|Escape sequence |Character name |Unicode encoding |
|\' |Single quote |0x0027 |
|\" |Double quote |0x0022 |
|\\ |Backslash |0x005C |
|\0 |Null |0x0000 |
|\a |Alert |0x0007 |
|\b |Backspace |0x0008 |
|\f |Form feed |0x000C |
|\n |New line |0x000A |
|\r |Carriage return |0x000D |
|\t |Horizontal tab |0x0009 |
|\v |Vertical tab |0x000B |

The type of a character-literal is char.

5 String literals

C# supports two forms of string literals: regular string literals and verbatim string literals.

A regular string literal consists of zero or more characters enclosed in double quotes, as in "hello", and may include both simple escape sequences (such as \t for the tab character), and hexadecimal and Unicode escape sequences.

A verbatim string literal consists of an @ character followed by a double-quote character, zero or more characters, and a closing double-quote character. A simple example is @"hello". In a verbatim string literal, the characters between the delimiters are interpreted verbatim, the only exception being a quote-escape-sequence. In particular, simple escape sequences, and hexadecimal and Unicode escape sequences are not processed in verbatim string literals. A verbatim string literal may span multiple lines.

string-literal: regular-string-literal verbatim-string-literal

regular-string-literal:
" regular-string-literal-charactersopt "

regular-string-literal-characters: regular-string-literal-character regular-string-literal-characters regular-string-literal-character

regular-string-literal-character: single-regular-string-literal-character simple-escape-sequence hexadecimal-escape-sequence unicode-escape-sequence

single-regular-string-literal-character:
Any character except " (U+0022), \ (U+005C), and new-line-character

verbatim-string-literal:
@" verbatim-string-literal-charactersopt "

verbatim-string-literal-characters: verbatim-string-literal-character verbatim-string-literal-characters verbatim-string-literal-character

verbatim-string-literal-character: single-verbatim-string-literal-character quote-escape-sequence

single-verbatim-string-literal-character:
Any character except "

quote-escape-sequence:
""

A character that follows a backslash character (\) in a regular-string-literal-character must be one of the following characters: ', ", \, 0, a, b, f, n, r, t, u, U, x, v. Otherwise, a compile-time error occurs.

The example

string a = "hello, world"; // hello, world string b = @"hello, world"; // hello, world

string c = "hello \t world"; // hello world string d = @"hello \t world"; // hello \t world

string e = "Joe said \"Hello\" to me"; // Joe said "Hello" to me string f = @"Joe said ""Hello"" to me"; // Joe said "Hello" to me

string g = "\\\\server\\share\\file.txt"; // \\server\share\file.txt string h = @"\\server\share\file.txt"; // \\server\share\file.txt

string i = "one\r\ntwo\r\nthree"; string j = @"one two three";

shows a variety of string literals. The last string literal, j, is a verbatim string literal that spans multiple lines. The characters between the quotation marks, including white space such as new line characters, are preserved verbatim.

Since a hexadecimal escape sequence can have a variable number of hex digits, the string literal "\x123" contains a single character with hex value 123. To create a string containing the character with hex value 12 followed by the character 3, one could write "\x00123" or "\x12" + "3" instead.

The type of a string-literal is string.

Each string literal does not necessarily result in a new string instance. When two or more string literals that are equivalent according to the string equality operator (§7.10.7) appear in the same program, these string literals refer to the same string instance. For instance, the output produced by

class Test
{
static void Main() { object a = "hello"; object b = "hello"; System.Console.WriteLine(a == b); }
}

is True because the two literals refer to the same string instance.

6 The null literal

null-literal: null The null-literal can be implicitly converted to a reference type or nullable type.

5 Operators and punctuators

There are several kinds of operators and punctuators. Operators are used in expressions to describe operations involving one or more operands. For example, the expression a + b uses the + operator to add the two operands a and b. Punctuators are for grouping and separating.

operator-or-punctuator: one of
{ } [ ] ( ) . , : ;
+ - * / % & | ^ ! ~
= < > ? ?? :: ++ -- && ||
-> == != = += -= *= /= %=
&= |= ^=

right-shift-assignment:
>|>=

The vertical bar in the right-shift and right-shift-assignment productions are used to indicate that, unlike other productions in the syntactic grammar, no characters of any kind (not even whitespace) are allowed between the tokens. These productions are treated specially in order to enable the correct handling of type-parameter-lists (§10.1.3).

5 Pre-processing directives

The pre-processing directives provide the ability to conditionally skip sections of source files, to report error and warning conditions, and to delineate distinct regions of source code. The term “pre-processing directives” is used only for consistency with the C and C++ programming languages. In C#, there is no separate pre-processing step; pre-processing directives are processed as part of the lexical analysis phase.

pp-directive: pp-declaration pp-conditional pp-line pp-diagnostic pp-region pp-pragma

The following pre-processing directives are available:

#define and #undef, which are used to define and undefine, respectively, conditional compilation symbols (§2.5.3).

#if, #elif, #else, and #endif, which are used to conditionally skip sections of source code (§2.5.4).

#line, which is used to control line numbers emitted for errors and warnings (§2.5.7).

#error and #warning, which are used to issue errors and warnings, respectively (§2.5.5).

#region and #endregion, which are used to explicitly mark sections of source code (§2.5.6).

#pragma, which is used to specify optional contextual information to the compiler (§2.5.8).

A pre-processing directive always occupies a separate line of source code and always begins with a # character and a pre-processing directive name. White space may occur before the # character and between the # character and the directive name.

A source line containing a #define, #undef, #if, #elif, #else, #endif, or #line directive may end with a single-line comment. Delimited comments (the /* */ style of comments) are not permitted on source lines containing pre-processing directives.

Pre-processing directives are not tokens and are not part of the syntactic grammar of C#. However, pre-processing directives can be used to include or exclude sequences of tokens and can in that way affect the meaning of a C# program. For example, when compiled, the program:

#define A
#undef B

class C
{
#if A void F() {}
#else
void G() {}
#endif

#if B void H() {}
#else
void I() {}
#endif
}

results in the exact same sequence of tokens as the program:

class C
{
void F() {} void I() {}
}

Thus, whereas lexically, the two programs are quite different, syntactically, they are identical.

1 Conditional compilation symbols

The conditional compilation functionality provided by the #if, #elif, #else, and #endif directives is controlled through pre-processing expressions (§2.5.2) and conditional compilation symbols.

conditional-symbol:
Any identifier-or-keyword except true or false

A conditional compilation symbol has two possible states: defined or undefined. At the beginning of the lexical processing of a source file, a conditional compilation symbol is undefined unless it has been explicitly defined by an external mechanism (such as a command-line compiler option). When a #define directive is processed, the conditional compilation symbol named in that directive becomes defined in that source file. The symbol remains defined until an #undef directive for that same symbol is processed, or until the end of the source file is reached. An implication of this is that #define and #undef directives in one source file have no effect on other source files in the same program.

When referenced in a pre-processing expression, a defined conditional compilation symbol has the boolean value true, and an undefined conditional compilation symbol has the boolean value false. There is no requirement that conditional compilation symbols be explicitly declared before they are referenced in pre-processing expressions. Instead, undeclared symbols are simply undefined and thus have the value false.

The name space for conditional compilation symbols is distinct and separate from all other named entities in a C# program. Conditional compilation symbols can only be referenced in #define and #undef directives and in pre-processing expressions.

2 Pre-processing expressions

Pre-processing expressions can occur in #if and #elif directives. The operators !, ==, !=, && and || are permitted in pre-processing expressions, and parentheses may be used for grouping.

pp-expression: whitespaceopt pp-or-expression whitespaceopt

pp-or-expression: pp-and-expression pp-or-expression whitespaceopt || whitespaceopt pp-and-expression

pp-and-expression: pp-equality-expression pp-and-expression whitespaceopt && whitespaceopt pp-equality-expression

pp-equality-expression: pp-unary-expression pp-equality-expression whitespaceopt == whitespaceopt pp-unary-expression pp-equality-expression whitespaceopt != whitespaceopt pp-unary-expression

pp-unary-expression: pp-primary-expression ! whitespaceopt pp-unary-expression

pp-primary-expression: true false conditional-symbol ( whitespaceopt pp-expression whitespaceopt )

When referenced in a pre-processing expression, a defined conditional compilation symbol has the boolean value true, and an undefined conditional compilation symbol has the boolean value false.

Evaluation of a pre-processing expression always yields a boolean value. The rules of evaluation for a pre-processing expression are the same as those for a constant expression (§7.19), except that the only user-defined entities that can be referenced are conditional compilation symbols.

3 Declaration directives

The declaration directives are used to define or undefine conditional compilation symbols.

pp-declaration: whitespaceopt # whitespaceopt define whitespace conditional-symbol pp-new-line whitespaceopt # whitespaceopt undef whitespace conditional-symbol pp-new-line

pp-new-line: whitespaceopt single-line-commentopt new-line

The processing of a #define directive causes the given conditional compilation symbol to become defined, starting with the source line that follows the directive. Likewise, the processing of an #undef directive causes the given conditional compilation symbol to become undefined, starting with the source line that follows the directive.

Any #define and #undef directives in a source file must occur before the first token (§2.4) in the source file; otherwise a compile-time error occurs. In intuitive terms, #define and #undef directives must precede any “real code” in the source file.

The example:

#define Enterprise

#if Professional || Enterprise #define Advanced
#endif

namespace Megacorp.Data
{
#if Advanced class PivotTable {...} #endif
}

is valid because the #define directives precede the first token (the namespace keyword) in the source file.

The following example results in a compile-time error because a #define follows real code:

#define A namespace N
{
#define B #if B class Class1 {} #endif
}

A #define may define a conditional compilation symbol that is already defined, without there being any intervening #undef for that symbol. The example below defines a conditional compilation symbol A and then defines it again.

#define A
#define A

A #undef may “undefine” a conditional compilation symbol that is not defined. The example below defines a conditional compilation symbol A and then undefines it twice; although the second #undef has no effect, it is still valid.

#define A
#undef A
#undef A

4 Conditional compilation directives

The conditional compilation directives are used to conditionally include or exclude portions of a source file.

pp-conditional: pp-if-section pp-elif-sectionsopt pp-else-sectionopt pp-endif

pp-if-section: whitespaceopt # whitespaceopt if whitespace pp-expression pp-new-line conditional-sectionopt

pp-elif-sections: pp-elif-section pp-elif-sections pp-elif-section

pp-elif-section: whitespaceopt # whitespaceopt elif whitespace pp-expression pp-new-line conditional-sectionopt

pp-else-section: whitespaceopt # whitespaceopt else pp-new-line conditional-sectionopt

pp-endif: whitespaceopt # whitespaceopt endif pp-new-line

conditional-section: input-section skipped-section

skipped-section: skipped-section-part skipped-section skipped-section-part

skipped-section-part: skipped-charactersopt new-line pp-directive skipped-characters: whitespaceopt not-number-sign input-charactersopt

not-number-sign:
Any input-character except #

As indicated by the syntax, conditional compilation directives must be written as sets consisting of, in order, an #if directive, zero or more #elif directives, zero or one #else directive, and an #endif directive. Between the directives are conditional sections of source code. Each section is controlled by the immediately preceding directive. A conditional section may itself contain nested conditional compilation directives provided these directives form complete sets.

A pp-conditional selects at most one of the contained conditional-sections for normal lexical processing:

The pp-expressions of the #if and #elif directives are evaluated in order until one yields true. If an expression yields true, the conditional-section of the corresponding directive is selected.

If all pp-expressions yield false, and if an #else directive is present, the conditional-section of the #else directive is selected.

Otherwise, no conditional-section is selected.

The selected conditional-section, if any, is processed as a normal input-section: the source code contained in the section must adhere to the lexical grammar; tokens are generated from the source code in the section; and pre-processing directives in the section have the prescribed effects.

The remaining conditional-sections, if any, are processed as skipped-sections: except for pre-processing directives, the source code in the section need not adhere to the lexical grammar; no tokens are generated from the source code in the section; and pre-processing directives in the section must be lexically correct but are not otherwise processed. Within a conditional-section that is being processed as a skipped-section, any nested conditional-sections (contained in nested #if...#endif and #region...#endregion constructs) are also processed as skipped-sections.

The following example illustrates how conditional compilation directives can nest:

#define Debug // Debugging on
#undef Trace // Tracing off

class PurchaseTransaction
{
void Commit() { #if Debug CheckConsistency(); #if Trace WriteToLog(this.ToString()); #endif #endif CommitHelper(); }
}

Except for pre-processing directives, skipped source code is not subject to lexical analysis. For example, the following is valid despite the unterminated comment in the #else section:

#define Debug // Debugging on

class PurchaseTransaction
{
void Commit() { #if Debug CheckConsistency(); #else /* Do something else #endif }
}

Note, however, that pre-processing directives are required to be lexically correct even in skipped sections of source code.

Pre-processing directives are not processed when they appear inside multi-line input elements. For example, the program:

class Hello
{
static void Main() { System.Console.WriteLine(@"hello,
#if Debug world
#else
Nebraska
#endif
"); }
}

results in the output:

hello,
#if Debug world
#else
Nebraska
#endif

In peculiar cases, the set of pre-processing directives that is processed might depend on the evaluation of the pp-expression. The example:

#if X /*
#else
/* */ class Q { }
#endif

always produces the same token stream (class Q { }), regardless of whether or not X is defined. If X is defined, the only processed directives are #if and #endif, due to the multi-line comment. If X is undefined, then three directives (#if, #else, #endif) are part of the directive set.

5 Diagnostic directives

The diagnostic directives are used to explicitly generate error and warning messages that are reported in the same way as other compile-time errors and warnings.

pp-diagnostic: whitespaceopt # whitespaceopt error pp-message whitespaceopt # whitespaceopt warning pp-message

pp-message: new-line whitespace input-charactersopt new-line

The example:

#warning Code review needed before check-in

#if Debug && Retail #error A build can't be both debug and retail
#endif

class Test {...}

always produces a warning (“Code review needed before check-in”), and produces a compile-time error (“A build can’t be both debug and retail”) if the conditional symbols Debug and Retail are both defined. Note that a pp-message can contain arbitrary text; specifically, it need not contain well-formed tokens, as shown by the single quote in the word can’t.

6 Region directives

The region directives are used to explicitly mark regions of source code.

pp-region: pp-start-region conditional-sectionopt pp-end-region

pp-start-region: whitespaceopt # whitespaceopt region pp-message

pp-end-region: whitespaceopt # whitespaceopt endregion pp-message

No semantic meaning is attached to a region; regions are intended for use by the programmer or by automated tools to mark a section of source code. The message specified in a #region or #endregion directive likewise has no semantic meaning; it merely serves to identify the region. Matching #region and #endregion directives may have different pp-messages.

The lexical processing of a region:

#region
...
#endregion

corresponds exactly to the lexical processing of a conditional compilation directive of the form:

#if true
...
#endif

7 Line directives

Line directives may be used to alter the line numbers and source file names that are reported by the compiler in output such as warnings and errors.

Line directives are most commonly used in meta-programming tools that generate C# source code from some other text input.

pp-line: whitespaceopt # whitespaceopt line whitespace line-indicator pp-new-line

line-indicator: decimal-digits whitespace file-name decimal-digits default hidden file-name:
" file-name-characters "

file-name-characters: file-name-character file-name-characters file-name-character

file-name-character:
Any input-character except "

When no #line directives are present, the compiler reports true line numbers and source file names in its output. When processing a #line directive that includes a line-indicator that is not default, the compiler treats the line after the directive as having the given line number (and file name, if specified).

A #line default directive reverses the effect of all preceding #line directives. The compiler reports true line information for subsequent lines, precisely as if no #line directives had been processed.

A #line hidden directive has no effect on the file and line numbers reported in error messages, but does affect source level debugging. When debugging, all lines between a #line hidden directive and the subsequent #line directive (that is not #line hidden) have no line number information. When stepping through code in the debugger, these lines will be skipped entirely.

Note that a file-name differs from a regular string literal in that escape characters are not processed; the ‘\’ character simply designates an ordinary backslash character within a file-name.

8 Pragma directives

The #pragma preprocessing directive is used to specify optional contextual information to the compiler. The information supplied in a #pragma directive will never change program semantics.

pp-pragma: whitespaceopt # whitespaceopt pragma whitespace pragma-body pp-new-line

pragma-body: pragma-warning-body C# provides #pragma directives to control compiler warnings. Future versions of the language may include additional #pragma directives. To ensure interoperability with other C# compilers, the Microsoft C# compiler does not issue compilation errors for unknown #pragma directives; such directives do however generate warnings.

1 Pragma warning

The #pragma warning directive is used to disable or restore all or a particular set of warning messages during compilation of the subsequent program text.

pragma-warning-body: warning whitespace warning-action warning whitespace warning-action whitespace warning-list

warning-action: disable restore

warning-list: decimal-digits warning-list whitespaceopt , whitespaceopt decimal-digits

A #pragma warning directive that omits the warning list affects all warnings. A #pragma warning directive the includes a warning list affects only those warnings that are specified in the list.

A #pragma warning disable directive disables all or the given set of warnings.

A #pragma warning restore directive restores all or the given set of warnings to the state that was in effect at the beginning of the compilation unit. Note that if a particular warning was disabled externally, a #pragma warning restore (whether for all or the specific warning) will not re-enable that warning.

The following example shows use of #pragma warning to temporarily disable the warning reported when obsoleted members are referenced, using the warning number from the Microsoft C# compiler.

using System;

class Program
{
[Obsolete] static void Foo() {}

static void Main() {
#pragma warning disable 612 Foo();
#pragma warning restore 612 }
}

Basic concepts

1 Application Startup

An assembly that has an entry point is called an application. When an application is run, a new application domain is created. Several different instantiations of an application may exist on the same machine at the same time, and each has its own application domain.

An application domain enables application isolation by acting as a container for application state. An application domain acts as a container and boundary for the types defined in the application and the class libraries it uses. Types loaded into one application domain are distinct from the same type loaded into another application domain, and instances of objects are not directly shared between application domains. For instance, each application domain has its own copy of static variables for these types, and a static constructor for a type is run at most once per application domain. Implementations are free to provide implementation-specific policy or mechanisms for the creation and destruction of application domains.

Application startup occurs when the execution environment calls a designated method, which is referred to as the application's entry point. This entry point method is always named Main, and can have one of the following signatures:

static void Main() {...}

static void Main(string[] args) {...}

static int Main() {...}

static int Main(string[] args) {...}

As shown, the entry point may optionally return an int value. This return value is used in application termination (§3.2).

The entry point may optionally have one formal parameter. The parameter may have any name, but the type of the parameter must be string[]. If the formal parameter is present, the execution environment creates and passes a string[] argument containing the command-line arguments that were specified when the application was started. The string[] argument is never null, but it may have a length of zero if no command-line arguments were specified.

Since C# supports method overloading, a class or struct may contain multiple definitions of some method, provided each has a different signature. However, within a single program, no class or struct may contain more than one method called Main whose definition qualifies it to be used as an application entry point. Other overloaded versions of Main are permitted, however, provided they have more than one parameter, or their only parameter is other than type string[].

An application can be made up of multiple classes or structs. It is possible for more than one of these classes or structs to contain a method called Main whose definition qualifies it to be used as an application entry point. In such cases, an external mechanism (such as a command-line compiler option) must be used to select one of these Main methods as the entry point.

In C#, every method must be defined as a member of a class or struct. Ordinarily, the declared accessibility (§3.5.1) of a method is determined by the access modifiers (§10.3.5) specified in its declaration, and similarly the declared accessibility of a type is determined by the access modifiers specified in its declaration. In order for a given method of a given type to be callable, both the type and the member must be accessible. However, the application entry point is a special case. Specifically, the execution environment can access the application's entry point regardless of its declared accessibility and regardless of the declared accessibility of its enclosing type declarations.

The application entry point method may not be in a generic class declaration.

In all other respects, entry point methods behave like those that are not entry points.

2 Application termination

Application termination returns control to the execution environment.

If the return type of the application’s entry point method is int, the value returned serves as the application's termination status code. The purpose of this code is to allow communication of success or failure to the execution environment.

If the return type of the entry point method is void, reaching the right brace (}) which terminates that method, or executing a return statement that has no expression, results in a termination status code of 0.

Prior to an application’s termination, destructors for all of its objects that have not yet been garbage collected are called, unless such cleanup has been suppressed (by a call to the library method GC.SuppressFinalize, for example).

3 Declarations

Declarations in a C# program define the constituent elements of the program. C# programs are organized using namespaces (§9), which can contain type declarations and nested namespace declarations. Type declarations (§9.6) are used to define classes (§10), structs (§10.14), interfaces (§13), enums (§14), and delegates (§15). The kinds of members permitted in a type declaration depend on the form of the type declaration. For instance, class declarations can contain declarations for constants (§10.4), fields (§10.5), methods (§10.6), properties (§10.7), events (§10.8), indexers (§10.9), operators (§10.10), instance constructors (§10.11), static constructors (§10.12), destructors (§10.13), and nested types(§10.3.8).

A declaration defines a name in the declaration space to which the declaration belongs. Except for overloaded members (§3.6), it is a compile-time error to have two or more declarations that introduce members with the same name in a declaration space. It is never possible for a declaration space to contain different kinds of members with the same name. For example, a declaration space can never contain a field and a method by the same name.

There are several different types of declaration spaces, as described in the following.

Within all source files of a program, namespace-member-declarations with no enclosing namespace-declaration are members of a single combined declaration space called the global declaration space.

Within all source files of a program, namespace-member-declarations within namespace-declarations that have the same fully qualified namespace name are members of a single combined declaration space.

Each class, struct, or interface declaration creates a new declaration space. Names are introduced into this declaration space through class-member-declarations, struct-member-declarations, interface-member-declarations, or type-parameters. Except for overloaded instance constructor declarations and static constructor declarations, a class or struct cannot contain a member declaration with the same name as the class or struct. A class, struct, or interface permits the declaration of overloaded methods and indexers. Furthermore, a class or struct permits the declaration of overloaded instance constructors and operators. For example, a class, struct, or interface may contain multiple method declarations with the same name, provided these method declarations differ in their signature (§3.6). Note that base classes do not contribute to the declaration space of a class, and base interfaces do not contribute to the declaration space of an interface. Thus, a derived class or interface is allowed to declare a member with the same name as an inherited member. Such a member is said to hide the inherited member.

Each delegate declaration creates a new declaration space. Names are introduced into this declaration space through formal parameters (fixed-parameters and parameter-arrays) and type-parameters.

Each enumeration declaration creates a new declaration space. Names are introduced into this declaration space through enum-member-declarations.

Each method declaration, indexer declaration, operator declaration, instance constructor declaration and anonymous function creates a new declaration space called a local variable declaration space. Names are introduced into this declaration space through formal parameters (fixed-parameters and parameter-arrays) and type-parameters. The body of the function member or anonymous function, if any, is considered to be nested within the local variable declaration space. It is an error for a local variable declaration space and a nested local variable declaration space to contain elements with the same name. Thus, within a nested declaration space it is not possible to declare a local variable or constant with the same name as a local variable or constant in an enclosing declaration space. It is possible for two declaration spaces to contain elements with the same name as long as neither declaration space contains the other.

Each block or switch-block , as well as a for, foreach and using statement, creates a local variable declaration space for local variables and local constants . Names are introduced into this declaration space through local-variable-declarations and local-constant-declarations. Note that blocks that occur as or within the body of a function member or anonymous function are nested within the local variable declaration space declared by those functions for their parameters. Thus it is an error to have e.g. a method with a local variable and a parameter of the same name.

Each block or switch-block creates a separate declaration space for labels. Names are introduced into this declaration space through labeled-statements, and the names are referenced through goto-statements. The label declaration space of a block includes any nested blocks. Thus, within a nested block it is not possible to declare a label with the same name as a label in an enclosing block.

The textual order in which names are declared is generally of no significance. In particular, textual order is not significant for the declaration and use of namespaces, constants, methods, properties, events, indexers, operators, instance constructors, destructors, static constructors, and types. Declaration order is significant in the following ways:

Declaration order for field declarations and local variable declarations determines the order in which their initializers (if any) are executed.

Local variables must be defined before they are used (§3.7).

Declaration order for enum member declarations (§14.3) is significant when constant-expression values are omitted.

The declaration space of a namespace is “open ended”, and two namespace declarations with the same fully qualified name contribute to the same declaration space. For example

namespace Megacorp.Data
{
class Customer { ... }
}

namespace Megacorp.Data
{
class Order { ... }
}

The two namespace declarations above contribute to the same declaration space, in this case declaring two classes with the fully qualified names Megacorp.Data.Customer and Megacorp.Data.Order. Because the two declarations contribute to the same declaration space, it would have caused a compile-time error if each contained a declaration of a class with the same name.

As specified above, the declaration space of a block includes any nested blocks. Thus, in the following example, the F and G methods result in a compile-time error because the name i is declared in the outer block and cannot be redeclared in the inner block. However, the H and I methods are valid since the two i’s are declared in separate non-nested blocks.

class A
{
void F() { int i = 0; if (true) { int i = 1; } }

void G() { if (true) { int i = 0; } int i = 1; }

void H() { if (true) { int i = 0; } if (true) { int i = 1; } }

void I() { for (int i = 0; i < 10; i++) H(); for (int i = 0; i < 10; i++) H(); }
}

4 Members

Namespaces and types have members. The members of an entity are generally available through the use of a qualified name that starts with a reference to the entity, followed by a “.” token, followed by the name of the member.

Members of a type are either declared in the type declaration or inherited from the base class of the type. When a type inherits from a base class, all members of the base class, except instance constructors, destructors and static constructors, become members of the derived type. The declared accessibility of a base class member does not control whether the member is inherited—inheritance extends to any member that isn’t an instance constructor, static constructor, or destructor. However, an inherited member may not be accessible in a derived type, either because of its declared accessibility (§3.5.1) or because it is hidden by a declaration in the type itself (§3.7.1.2).

1 Namespace members

Namespaces and types that have no enclosing namespace are members of the global namespace. This corresponds directly to the names declared in the global declaration space.

Namespaces and types declared within a namespace are members of that namespace. This corresponds directly to the names declared in the declaration space of the namespace.

Namespaces have no access restrictions. It is not possible to declare private, protected, or internal namespaces, and namespace names are always publicly accessible.

2 Struct members

The members of a struct are the members declared in the struct and the members inherited from the struct’s direct base class System.ValueType and the indirect base class object.

The members of a simple type correspond directly to the members of the struct type aliased by the simple type:

The members of sbyte are the members of the System.SByte struct.

The members of byte are the members of the System.Byte struct.

The members of short are the members of the System.Int16 struct.

The members of ushort are the members of the System.UInt16 struct.

The members of int are the members of the System.Int32 struct.

The members of uint are the members of the System.UInt32 struct.

The members of long are the members of the System.Int64 struct.

The members of ulong are the members of the System.UInt64 struct.

The members of char are the members of the System.Char struct.

The members of float are the members of the System.Single struct.

The members of double are the members of the System.Double struct.

The members of decimal are the members of the System.Decimal struct.

The members of bool are the members of the System.Boolean struct.

3 Enumeration members

The members of an enumeration are the constants declared in the enumeration and the members inherited from the enumeration’s direct base class System.Enum and the indirect base classes System.ValueType and object.

4 Class members

The members of a class are the members declared in the class and the members inherited from the base class (except for class object which has no base class). The members inherited from the base class include the constants, fields, methods, properties, events, indexers, operators, and types of the base class, but not the instance constructors, destructors and static constructors of the base class. Base class members are inherited without regard to their accessibility.

A class declaration may contain declarations of constants, fields, methods, properties, events, indexers, operators, instance constructors, destructors, static constructors and types.

The members of object and string correspond directly to the members of the class types they alias:

The members of object are the members of the System.Object class.

The members of string are the members of the System.String class.

5 Interface members

The members of an interface are the members declared in the interface and in all base interfaces of the interface. The members in class object are not, strictly speaking, members of any interface (§13.2). However, the members in class object are available via member lookup in any interface type (§7.4).

6 Array members

The members of an array are the members inherited from class System.Array.

7 Delegate members

The members of a delegate are the members inherited from class System.Delegate.

5 Member access

Declarations of members allow control over member access. The accessibility of a member is established by the declared accessibility (§3.5.1) of the member combined with the accessibility of the immediately containing type, if any.

When access to a particular member is allowed, the member is said to be accessible. Conversely, when access to a particular member is disallowed, the member is said to be inaccessible. Access to a member is permitted when the textual location in which the access takes place is included in the accessibility domain (§3.5.2) of the member.

1 Declared accessibility

The declared accessibility of a member can be one of the following:

Public, which is selected by including a public modifier in the member declaration. The intuitive meaning of public is “access not limited”.

Protected, which is selected by including a protected modifier in the member declaration. The intuitive meaning of protected is “access limited to the containing class or types derived from the containing class”.

Internal, which is selected by including an internal modifier in the member declaration. The intuitive meaning of internal is “access limited to this program”.

Protected internal (meaning protected or internal), which is selected by including both a protected and an internal modifier in the member declaration. The intuitive meaning of protected internal is “access limited to this program or types derived from the containing class”.

Private, which is selected by including a private modifier in the member declaration. The intuitive meaning of private is “access limited to the containing type”.

Depending on the context in which a member declaration takes place, only certain types of declared accessibility are permitted. Furthermore, when a member declaration does not include any access modifiers, the context in which the declaration takes place determines the default declared accessibility.

Namespaces implicitly have public declared accessibility. No access modifiers are allowed on namespace declarations.

Types declared in compilation units or namespaces can have public or internal declared accessibility and default to internal declared accessibility.

Class members can have any of the five kinds of declared accessibility and default to private declared accessibility. (Note that a type declared as a member of a class can have any of the five kinds of declared accessibility, whereas a type declared as a member of a namespace can have only public or internal declared accessibility.)

Struct members can have public, internal, or private declared accessibility and default to private declared accessibility because structs are implicitly sealed. Struct members introduced in a struct (that is, not inherited by that struct) cannot have protected or protected internal declared accessibility. (Note that a type declared as a member of a struct can have public, internal, or private declared accessibility, whereas a type declared as a member of a namespace can have only public or internal declared accessibility.)

Interface members implicitly have public declared accessibility. No access modifiers are allowed on interface member declarations.

Enumeration members implicitly have public declared accessibility. No access modifiers are allowed on enumeration member declarations.

2 Accessibility domains

The accessibility domain of a member consists of the (possibly disjoint) sections of program text in which access to the member is permitted. For purposes of defining the accessibility domain of a member, a member is said to be top-level if it is not declared within a type, and a member is said to be nested if it is declared within another type. Furthermore, the program text of a program is defined as all program text contained in all source files of the program, and the program text of a type is defined as all program text contained in the type-declarations of that type (including, possibly, types that are nested within the type).

The accessibility domain of a predefined type (such as object, int, or double) is unlimited.

The accessibility domain of a top-level unbound type T (§4.4.3) that is declared in a program P is defined as follows:

If the declared accessibility of T is public, the accessibility domain of T is the program text of P and any program that references P.

If the declared accessibility of T is internal, the accessibility domain of T is the program text of P.

From these definitions it follows that the accessibility domain of a top-level unbound type is always at least the program text of the program in which that type is declared.

The accessibility domain for a constructed type T is the intersection of the accessibility domain of the unbound generic type T and the accessibility domains of the type arguments A1, ...,AN.

The accessibility domain of a nested member M declared in a type T within a program P is defined as follows (noting that M itself may possibly be a type):

If the declared accessibility of M is public, the accessibility domain of M is the accessibility domain of T.

If the declared accessibility of M is protected internal, let D be the union of the program text of P and the program text of any type derived from T, which is declared outside P. The accessibility domain of M is the intersection of the accessibility domain of T with D.

If the declared accessibility of M is protected, let D be the union of the program text of T and the program text of any type derived from T. The accessibility domain of M is the intersection of the accessibility domain of T with D.

If the declared accessibility of M is internal, the accessibility domain of M is the intersection of the accessibility domain of T with the program text of P.

If the declared accessibility of M is private, the accessibility domain of M is the program text of T.

From these definitions it follows that the accessibility domain of a nested member is always at least the program text of the type in which the member is declared. Furthermore, it follows that the accessibility domain of a member is never more inclusive than the accessibility domain of the type in which the member is declared.

In intuitive terms, when a type or member M is accessed, the following steps are evaluated to ensure that the access is permitted:

First, if M is declared within a type (as opposed to a compilation unit or a namespace), a compile-time error occurs if that type is not accessible.

Then, if M is public, the access is permitted.

Otherwise, if M is protected internal, the access is permitted if it occurs within the program in which M is declared, or if it occurs within a class derived from the class in which M is declared and takes place through the derived class type (§3.5.3).

Otherwise, if M is protected, the access is permitted if it occurs within the class in which M is declared, or if it occurs within a class derived from the class in which M is declared and takes place through the derived class type (§3.5.3).

Otherwise, if M is internal, the access is permitted if it occurs within the program in which M is declared.

Otherwise, if M is private, the access is permitted if it occurs within the type in which M is declared.

Otherwise, the type or member is inaccessible, and a compile-time error occurs.

In the example

public class A
{
public static int X; internal static int Y; private static int Z;
}

internal class B
{
public static int X; internal static int Y; private static int Z;

public class C { public static int X; internal static int Y; private static int Z; }

private class D { public static int X; internal static int Y; private static int Z; }
}

the classes and members have the following accessibility domains:

The accessibility domain of A and A.X is unlimited.

The accessibility domain of A.Y, B, B.X, B.Y, B.C, B.C.X, and B.C.Y is the program text of the containing program.

The accessibility domain of A.Z is the program text of A.

The accessibility domain of B.Z and B.D is the program text of B, including the program text of B.C and B.D.

The accessibility domain of B.C.Z is the program text of B.C.

The accessibility domain of B.D.X and B.D.Y is the program text of B, including the program text of B.C and B.D.

The accessibility domain of B.D.Z is the program text of B.D.

As the example illustrates, the accessibility domain of a member is never larger than that of a containing type. For example, even though all X members have public declared accessibility, all but A.X have accessibility domains that are constrained by a containing type.

As described in §3.4, all members of a base class, except for instance constructors, destructors and static constructors, are inherited by derived types. This includes even private members of a base class. However, the accessibility domain of a private member includes only the program text of the type in which the member is declared. In the example

class A
{
int x;

static void F(B b) { b.x = 1; // Ok }
}

class B: A
{
static void F(B b) { b.x = 1; // Error, x not accessible }
}

the B class inherits the private member x from the A class. Because the member is private, it is only accessible within the class-body of A. Thus, the access to b.x succeeds in the A.F method, but fails in the B.F method.

3 Protected access for instance members

When a protected instance member is accessed outside the program text of the class in which it is declared, and when a protected internal instance member is accessed outside the program text of the program in which it is declared, the access must take place within a class declaration that derives from the class in which it is declared. Furthermore, the access is required to take place through an instance of that derived class type or a class type constructed from it. This restriction prevents one derived class from accessing protected members of other derived classes, even when the members are inherited from the same base class.

Let B be a base class that declares a protected instance member M, and let D be a class that derives from B. Within the class-body of D, access to M can take one of the following forms:

An unqualified type-name or primary-expression of the form M.

A primary-expression of the form E.M, provided the type of E is T or a class derived from T, where T is the class type D, or a class type constructed from D

A primary-expression of the form base.M.

In addition to these forms of access, a derived class can access a protected instance constructor of a base class in a constructor-initializer (§10.11.1).

In the example

public class A
{
protected int x;

static void F(A a, B b) { a.x = 1; // Ok b.x = 1; // Ok }
}

public class B: A
{
static void F(A a, B b) { a.x = 1; // Error, must access through instance of B b.x = 1; // Ok }
}

within A, it is possible to access x through instances of both A and B, since in either case the access takes place through an instance of A or a class derived from A. However, within B, it is not possible to access x through an instance of A, since A does not derive from B.

In the example

class C
{
protected T x;
}

class D: C
{
static void F() { D dt = new D(); D di = new D(); D ds = new D(); dt.x = default(T); di.x = 123; ds.x = "test"; }
}

the three assignments to x are permitted because they all take place through instances of class types constructed from the generic type.

4 Accessibility constraints

Several constructs in the C# language require a type to be at least as accessible as a member or another type. A type T is said to be at least as accessible as a member or type M if the accessibility domain of T is a superset of the accessibility domain of M. In other words, T is at least as accessible as M if T is accessible in all contexts in which M is accessible.

The following accessibility constraints exist:

The direct base class of a class type must be at least as accessible as the class type itself.

The explicit base interfaces of an interface type must be at least as accessible as the interface type itself.

The return type and parameter types of a delegate type must be at least as accessible as the delegate type itself.

The type of a constant must be at least as accessible as the constant itself.

The type of a field must be at least as accessible as the field itself.

The return type and parameter types of a method must be at least as accessible as the method itself.

The type of a property must be at least as accessible as the property itself.

The type of an event must be at least as accessible as the event itself.

The type and parameter types of an indexer must be at least as accessible as the indexer itself.

The return type and parameter types of an operator must be at least as accessible as the operator itself.

The parameter types of an instance constructor must be at least as accessible as the instance constructor itself.

In the example

class A {...}

public class B: A {...}

the B class results in a compile-time error because A is not at least as accessible as B.

Likewise, in the example

class A {...}

public class B
{
A F() {...}

internal A G() {...}

public A H() {...}
}

the H method in B results in a compile-time error because the return type A is not at least as accessible as the method.

6 Signatures and overloading

Methods, instance constructors, indexers, and operators are characterized by their signatures:

The signature of a method consists of the name of the method, the number of type parameters and the type and kind (value, reference, or output) of each of its formal parameters, considered in the order left to right. For these purposes, any type parameter of the method that occurs in the type of a formal parameter is identified not by its name, but by its ordinal position in the type argument list of the method. The signature of a method specifically does not include the return type, the params modifier that may be specified for the right-most parameter, nor the optional type parameter constraints.

The signature of an instance constructor consists of the type and kind (value, reference, or output) of each of its formal parameters, considered in the order left to right. The signature of an instance constructor specifically does not include the params modifier that may be specified for the right-most parameter.

The signature of an indexer consists of the type of each of its formal parameters, considered in the order left to right. The signature of an indexer specifically does not include the element type, nor does it include the params modifier that may be specified for the right-most parameter.

The signature of an operator consists of the name of the operator and the type of each of its formal parameters, considered in the order left to right. The signature of an operator specifically does not include the result type.

Signatures are the enabling mechanism for overloading of members in classes, structs, and interfaces:

Overloading of methods permits a class, struct, or interface to declare multiple methods with the same name, provided their signatures are unique within that class, struct, or interface.

Overloading of instance constructors permits a class or struct to declare multiple instance constructors, provided their signatures are unique within that class or struct.

Overloading of indexers permits a class, struct, or interface to declare multiple indexers, provided their signatures are unique within that class, struct, or interface.

Overloading of operators permits a class or struct to declare multiple operators with the same name, provided their signatures are unique within that class or struct.

Although out and ref parameter modifiers are considered part of a signature, members declared in a single type cannot differ in signature solely by ref and out. A compile-time error occurs if two members are declared in the same type with signatures that would be the same if all parameters in both methods with out modifiers were changed to ref modifiers. For other purposes of signature matching (e.g., hiding or overriding), ref and out are considered part of the signature and do not match each other. (This restriction is to allow C# programs to be easily translated to run on the Common Language Infrastructure (CLI), which does not provide a way to define methods that differ solely in ref and out.)

For the purposes of singatures, the types object and dynamic are considered the same. Members declared in a single type can therefore not differ in signature solely by object and dynamic.

The following example shows a set of overloaded method declarations along with their signatures.

interface ITest
{
void F(); // F()

void F(int x); // F(int)

void F(ref int x); // F(ref int)

void F(out int x); // F(out int) error

void F(int x, int y); // F(int, int)

int F(string s); // F(string)

int F(int x); // F(int) error

void F(string[] a); // F(string[])

void F(params string[] a); // F(string[]) error
}

Note that any ref and out parameter modifiers (§10.6.1) are part of a signature. Thus, F(int) and F(ref int) are unique signatures. However, F(ref int) and F(out int) cannot be declared within the same interface because their signatures differ solely by ref and out. Also, note that the return type and the params modifier are not part of a signature, so it is not possible to overload solely based on return type or on the inclusion or exclusion of the params modifier. As such, the declarations of the methods F(int) and F(params string[]) identified above result in a compile-time error.

7 Scopes

The scope of a name is the region of program text within which it is possible to refer to the entity declared by the name without qualification of the name. Scopes can be nested, and an inner scope may redeclare the meaning of a name from an outer scope (this does not, however, remove the restriction imposed by §3.3 that within a nested block it is not possible to declare a local variable with the same name as a local variable in an enclosing block). The name from the outer scope is then said to be hidden in the region of program text covered by the inner scope, and access to the outer name is only possible by qualifying the name.

The scope of a namespace member declared by a namespace-member-declaration (§9.5) with no enclosing namespace-declaration is the entire program text.

The scope of a namespace member declared by a namespace-member-declaration within a namespace-declaration whose fully qualified name is N is the namespace-body of every namespace-declaration whose fully qualified name is N or starts with N, followed by a period.

The scope of name defined by an extern-alias-directive extends over the using-directives, global-attributes and namespace-member-declarations of its immediately containing compilation unit or namespace body. An extern-alias-directive does not contribute any new members to the underlying declaration space. In other words, an extern-alias-directive is not transitive, but, rather, affects only the compilation unit or namespace body in which it occurs.

The scope of a name defined or imported by a using-directive (§9.4) extends over the namespace-member-declarations of the compilation-unit or namespace-body in which the using-directive occurs. A using-directive may make zero or more namespace or type names available within a particular compilation-unit or namespace-body, but does not contribute any new members to the underlying declaration space. In other words, a using-directive is not transitive but rather affects only the compilation-unit or namespace-body in which it occurs.

The scope of a type parameter declared by a type-parameter-list on a class-declaration (§10.1) is the class-base, type-parameter-constraints-clauses, and class-body of that class-declaration.

The scope of a type parameter declared by a type-parameter-list on a struct-declaration (§11.1) is the struct-interfaces, type-parameter-constraints-clauses, and struct-body of that struct-declaration.

The scope of a type parameter declared by a type-parameter-list on an interface-declaration (§13.1) is the interface-base, type-parameter-constraints-clauses, and interface-body of that interface-declaration.

The scope of a type parameter declared by a type-parameter-list on a delegate-declaration (§15.1) is the return-type, formal-parameter-list, and type-parameter-constraints-clauses of that delegate-declaration.

The scope of a member declared by a class-member-declaration (§10.1.6) is the class-body in which the declaration occurs. In addition, the scope of a class member extends to the class-body of those derived classes that are included in the accessibility domain (§3.5.2) of the member.

The scope of a member declared by a struct-member-declaration (§11.2) is the struct-body in which the declaration occurs.

The scope of a member declared by an enum-member-declaration (§14.3) is the enum-body in which the declaration occurs.

The scope of a parameter declared in a method-declaration (§10.6) is the method-body of that method-declaration.

The scope of a parameter declared in an indexer-declaration (§10.9) is the accessor-declarations of that indexer-declaration.

The scope of a parameter declared in an operator-declaration (§10.10) is the block of that operator-declaration.

The scope of a parameter declared in a constructor-declaration (§10.11) is the constructor-initializer and block of that constructor-declaration.

The scope of a parameter declared in a lambda-expression (§) is the lambda-expression-body of that lambda-expression

The scope of a parameter declared in an anonymous-method-expression (§) is the block of that anonymous-method-expression.

The scope of a label declared in a labeled-statement (§8.4) is the block in which the declaration occurs.

The scope of a local variable declared in a local-variable-declaration (§8.5.1) is the block in which the declaration occurs.

The scope of a local variable declared in a switch-block of a switch statement (§8.7.2) is the switch-block.

The scope of a local variable declared in a for-initializer of a for statement (§8.8.3) is the for-initializer, the for-condition, the for-iterator, and the contained statement of the for statement.

The scope of a local constant declared in a local-constant-declaration (§8.5.2) is the block in which the declaration occurs. It is a compile-time error to refer to a local constant in a textual position that precedes its constant-declarator.

The scope of a variable declared as part of a foreach-statement, using-statement, lock-statement or query-expression is determined by the expansion of the given construct.

Within the scope of a namespace, class, struct, or enumeration member it is possible to refer to the member in a textual position that precedes the declaration of the member. For example

class A
{
void F() { i = 1; }

int i = 0;
}

Here, it is valid for F to refer to i before it is declared.

Within the scope of a local variable, it is a compile-time error to refer to the local variable in a textual position that precedes the local-variable-declarator of the local variable. For example

class A
{
int i = 0;

void F() { i = 1; // Error, use precedes declaration int i; i = 2; }

void G() { int j = (j = 1); // Valid }

void H() { int a = 1, b = ++a; // Valid }
}

In the F method above, the first assignment to i specifically does not refer to the field declared in the outer scope. Rather, it refers to the local variable and it results in a compile-time error because it textually precedes the declaration of the variable. In the G method, the use of j in the initializer for the declaration of j is valid because the use does not precede the local-variable-declarator. In the H method, a subsequent local-variable-declarator correctly refers to a local variable declared in an earlier local-variable-declarator within the same local-variable-declaration.

The scoping rules for local variables are designed to guarantee that the meaning of a name used in an expression context is always the same within a block. If the scope of a local variable were to extend only from its declaration to the end of the block, then in the example above, the first assignment would assign to the instance variable and the second assignment would assign to the local variable, possibly leading to compile-time errors if the statements of the block were later to be rearranged.

The meaning of a name within a block may differ based on the context in which the name is used. In the example

using System;

class A {}

class Test
{
static void Main() { string A = "hello, world"; string s = A; // expression context

Type t = typeof(A); // type context

Console.WriteLine(s); // writes "hello, world" Console.WriteLine(t); // writes "A" }
}

the name A is used in an expression context to refer to the local variable A and in a type context to refer to the class A.

1 Name hiding

The scope of an entity typically encompasses more program text than the declaration space of the entity. In particular, the scope of an entity may include declarations that introduce new declaration spaces containing entities of the same name. Such declarations cause the original entity to become hidden. Conversely, an entity is said to be visible when it is not hidden.

Name hiding occurs when scopes overlap through nesting and when scopes overlap through inheritance. The characteristics of the two types of hiding are described in the following sections.

1 Hiding through nesting

Name hiding through nesting can occur as a result of nesting namespaces or types within namespaces, as a result of nesting types within classes or structs, and as a result of parameter and local variable declarations.

In the example

class A
{
int i = 0;

void F() { int i = 1; }

void G() { i = 1; }
}

within the F method, the instance variable i is hidden by the local variable i, but within the G method, i still refers to the instance variable.

When a name in an inner scope hides a name in an outer scope, it hides all overloaded occurrences of that name. In the example

class Outer
{
static void F(int i) {}

static void F(string s) {}

class Inner { void G() { F(1); // Invokes Outer.Inner.F F("Hello"); // Error }

static void F(long l) {} }
}

the call F(1) invokes the F declared in Inner because all outer occurrences of F are hidden by the inner declaration. For the same reason, the call F("Hello") results in a compile-time error.

2 Hiding through inheritance

Name hiding through inheritance occurs when classes or structs redeclare names that were inherited from base classes. This type of name hiding takes one of the following forms:

A constant, field, property, event, or type introduced in a class or struct hides all base class members with the same name.

A method introduced in a class or struct hides all non-method base class members with the same name, and all base class methods with the same signature (method name and parameter count, modifiers, and types).

An indexer introduced in a class or struct hides all base class indexers with the same signature (parameter count and types).

The rules governing operator declarations (§10.10) make it impossible for a derived class to declare an operator with the same signature as an operator in a base class. Thus, operators never hide one another.

Contrary to hiding a name from an outer scope, hiding an accessible name from an inherited scope causes a warning to be reported. In the example

class Base
{
public void F() {}
}

class Derived: Base
{
public void F() {} // Warning, hiding an inherited name
}

the declaration of F in Derived causes a warning to be reported. Hiding an inherited name is specifically not an error, since that would preclude separate evolution of base classes. For example, the above situation might have come about because a later version of Base introduced an F method that wasn’t present in an earlier version of the class. Had the above situation been an error, then any change made to a base class in a separately versioned class library could potentially cause derived classes to become invalid.

The warning caused by hiding an inherited name can be eliminated through use of the new modifier:

class Base
{
public void F() {}
}

class Derived: Base
{
new public void F() {}
}

The new modifier indicates that the F in Derived is “new”, and that it is indeed intended to hide the inherited member.

A declaration of a new member hides an inherited member only within the scope of the new member.

class Base
{
public static void F() {}
}

class Derived: Base
{
new private static void F() {} // Hides Base.F in Derived only
}

class MoreDerived: Derived
{
static void G() { F(); } // Invokes Base.F
}

In the example above, the declaration of F in Derived hides the F that was inherited from Base, but since the new F in Derived has private access, its scope does not extend to MoreDerived. Thus, the call F() in MoreDerived.G is valid and will invoke Base.F.

8 Namespace and type names

Several contexts in a C# program require a namespace-name or a type-name to be specified.

namespace-name: namespace-or-type-name type-name: namespace-or-type-name namespace-or-type-name: identifier type-argument-listopt namespace-or-type-name . identifier type-argument-listopt qualified-alias-member A namespace-name is a namespace-or-type-name that refers to a namespace. Following resolution as described below, the namespace-or-type-name of a namespace-name must refer to a namespace, or otherwise a compile-time error occurs. No type arguments (§4.4.1) can be present in a namespace-name (only types can have type arguments).

A type-name is a namespace-or-type-name that refers to a type. Following resolution as described below, the namespace-or-type-name of a type-name must refer to a type, or otherwise a compile-time error occurs.

If the namespace-or-type-name is a qualified-alias-member its meaning is as described in §9.7. Otherwise, a namespace-or-type-name has one of four forms:

I

I

N.I

N.I

where I is a single identifier, N is a namespace-or-type-name and is an optional type-argument-list. When no type-argument-list is specified, consider K to be zero.

The meaning of a namespace-or-type-name is determined as follows:

If the namespace-or-type-name is of the form I or of the form I:

If K is zero and the namespace-or-type-name appears within a generic method declaration (§10.6) and if that declaration includes a type parameter (§10.1.3) with name I, then the namespace-or-type-name refers to that type parameter.

Otherwise, if the namespace-or-type-name appears within a type declaration, then for each instance type T (§10.3.1), starting with the instance type of that type declaration and continuing with the instance type of each enclosing class or struct declaration (if any):

If K is zero and the declaration of T includes a type parameter with name I, then the namespace-or-type-name refers to that type parameter.

Otherwise, if the namespace-or-type-name appears within the body of the type declaration, and T or any of its base types contain a nested accessible type having name I and K type parameters, then the namespace-or-type-name refers to that type constructed with the given type arguments. If there is more than one such type, the type declared within the more derived type is selected. Note that non-type members (constants, fields, methods, properties, indexers, operators, instance constructors, destructors, and static constructors) and type members with a different number of type parameters are ignored when determining the meaning of the namespace-or-type-name.

If the previous steps were unsuccessful then, for each namespace N, starting with the namespace in which the namespace-or-type-name occurs, continuing with each enclosing namespace (if any), and ending with the global namespace, the following steps are evaluated until an entity is located:

If K is zero and I is the name of a namespace in N, then:

If the location where the namespace-or-type-name occurs is enclosed by a namespace declaration for N and the namespace declaration contains an extern-alias-directive or using-alias-directive that associates the name I with a namespace or type, then the namespace-or-type-name is ambiguous and a compile-time error occurs.

Otherwise, the namespace-or-type-name refers to the namespace named I in N.

Otherwise, if N contains an accessible type having name I and K type parameters, then:

If K is zero and the location where the namespace-or-type-name occurs is enclosed by a namespace declaration for N and the namespace declaration contains an extern-alias-directive or using-alias-directive that associates the name I with a namespace or type, then the namespace-or-type-name is ambiguous and a compile-time error occurs.

Otherwise, the namespace-or-type-name refers to the type constructed with the given type arguments.

Otherwise, if the location where the namespace-or-type-name occurs is enclosed by a namespace declaration for N:

If K is zero and the namespace declaration contains an extern-alias-directive or using-alias-directive that associates the name I with an imported namespace or type, then the namespace-or-type-name refers to that namespace or type.

Otherwise, if the namespaces imported by the using-namespace-directives of the namespace declaration contain exactly one type having name I and K type parameters, then the namespace-or-type-name refers to that type constructed with the given type arguments.

Otherwise, if the namespaces imported by the using-namespace-directives of the namespace declaration contain more than one type having name I and K type parameters, then the namespace-or-type-name is ambiguous and an error occurs.

Otherwise, the namespace-or-type-name is undefined and a compile-time error occurs.

Otherwise, the namespace-or-type-name is of the form N.I or of the form N.I. N is first resolved as a namespace-or-type-name. If the resolution of N is not successful, a compile-time error occurs. Otherwise, N.I or N.I is resolved as follows:

If K is zero and N refers to a namespace and N contains a nested namespace with name I, then the namespace-or-type-name refers to that nested namespace.

Otherwise, if N refers to a namespace and N contains an accessible type having name I and K type parameters, then the namespace-or-type-name refers to that type constructed with the given type arguments.

Otherwise, if N refers to a (possibly constructed) class or struct type and N or any of its base classes contain a nested accessible type having name I and K type parameters, then the namespace-or-type-name refers to that type constructed with the given type arguments. If there is more than one such type, the type declared within the more derived type is selected. Note that if the meaning of N.I is being determined as part of resolving the base class specification of N then the direct base class of N is considered to be object (§10.1.4.1).

Otherwise, N.I is an invalid namespace-or-type-name, and a compile-time error occurs.

A namespace-or-type-name is permitted to reference a static class (§10.1.1.3) only if

The namespace-or-type-name is the T in a namespace-or-type-name of the form T.I, or

The namespace-or-type-name is the T in a typeof-expression (§7.5.11) of the form typeof(T).

1 Fully qualified names

Every namespace and type has a fully qualified name, which uniquely identifies the namespace or type amongst all others. The fully qualified name of a namespace or type N is determined as follows:

If N is a member of the global namespace, its fully qualified name is N.

Otherwise, its fully qualified name is S.N, where S is the fully qualified name of the namespace or type in which N is declared.

In other words, the fully qualified name of N is the complete hierarchical path of identifiers that lead to N, starting from the global namespace. Because every member of a namespace or type must have a unique name, it follows that the fully qualified name of a namespace or type is always unique.

The example below shows several namespace and type declarations along with their associated fully qualified names.

class A {} // A

namespace X // X
{
class B // X.B { class C {} // X.B.C }

namespace Y // X.Y { class D {} // X.Y.D }
}

namespace X.Y // X.Y
{
class E {} // X.Y.E
}

9 Automatic memory management

C# employs automatic memory management, which frees developers from manually allocating and freeing the memory occupied by objects. Automatic memory management policies are implemented by a garbage collector. The memory management life cycle of an object is as follows:

1. When the object is created, memory is allocated for it, the constructor is run, and the object is considered live.

If the object, or any part of it, cannot be accessed by any possible continuation of execution, other than the running of destructors, the object is considered no longer in use, and it becomes eligible for destruction. The C# compiler and the garbage collector may choose to analyze code to determine which references to an object may be used in the future. For instance, if a local variable that is in scope is the only existing reference to an object, but that local variable is never referred to in any possible continuation of execution from the current execution point in the procedure, the garbage collector may (but is not required to) treat the object as no longer in use.

Once the object is eligible for destruction, at some unspecified later time the destructor (§10.13) (if any) for the object is run. Unless overridden by explicit calls, the destructor for the object is run once only.

Once the destructor for an object is run, if that object, or any part of it, cannot be accessed by any possible continuation of execution, including the running of destructors, the object is considered inaccessible and the object becomes eligible for collection.

Finally, at some time after the object becomes eligible for collection, the garbage collector frees the memory associated with that object.

The garbage collector maintains information about object usage, and uses this information to make memory management decisions, such as where in memory to locate a newly created object, when to relocate an object, and when an object is no longer in use or inaccessible.

Like other languages that assume the existence of a garbage collector, C# is designed so that the garbage collector may implement a wide range of memory management policies. For instance, C# does not require that destructors be run or that objects be collected as soon as they are eligible, or that destructors be run in any particular order, or on any particular thread.

The behavior of the garbage collector can be controlled, to some degree, via static methods on the class System.GC. This class can be used to request a collection to occur, destructors to be run (or not run), and so forth.

Since the garbage collector is allowed wide latitude in deciding when to collect objects and run destructors, a conforming implementation may produce output that differs from that shown by the following code. The program

using System;

class A
{
~A() { Console.WriteLine("Destruct instance of A"); }
}

class B
{
object Ref;

public B(object o) { Ref = o; }

~B() { Console.WriteLine("Destruct instance of B"); }
}

class Test
{
static void Main() { B b = new B(new A()); b = null; GC.Collect(); GC.WaitForPendingFinalizers(); }
}

creates an instance of class A and an instance of class B. These objects become eligible for garbage collection when the variable b is assigned the value null, since after this time it is impossible for any user-written code to access them. The output could be either

Destruct instance of A
Destruct instance of B

or

Destruct instance of B
Destruct instance of A

because the language imposes no constraints on the order in which objects are garbage collected.

In subtle cases, the distinction between “eligible for destruction” and “eligible for collection” can be important. For example,

using System;

class A
{
~A() { Console.WriteLine("Destruct instance of A"); }

public void F() { Console.WriteLine("A.F"); Test.RefA = this; }
}

class B
{
public A Ref;

~B() { Console.WriteLine("Destruct instance of B"); Ref.F(); }
}

class Test
{
public static A RefA; public static B RefB;

static void Main() { RefB = new B(); RefA = new A(); RefB.Ref = RefA; RefB = null; RefA = null;

// A and B now eligible for destruction GC.Collect(); GC.WaitForPendingFinalizers();

// B now eligible for collection, but A is not if (RefA != null) Console.WriteLine("RefA is not null"); }
}

In the above program, if the garbage collector chooses to run the destructor of A before the destructor of B, then the output of this program might be:

Destruct instance of A
Destruct instance of B
A.F
RefA is not null

Note that although the instance of A was not in use and A’s destructor was run, it is still possible for methods of A (in this case, F) to be called from another destructor. Also, note that running of a destructor may cause an object to become usable from the mainline program again. In this case, the running of B’s destructor caused an instance of A that was previously not in use to become accessible from the live reference Test.RefA. After the call to WaitForPendingFinalizers, the instance of B is eligible for collection, but the instance of A is not, because of the reference Test.RefA.

To avoid confusion and unexpected behavior, it is generally a good idea for destructors to only perform cleanup on data stored in their object's own fields, and not to perform any actions on referenced objects or static fields.

An alternative to using destructors is to let a class implement the System.IDisposable interface. This allows the client of the object to determine when to release the resources of the object, typically by accessing the object as a resource in a using statement (§8.13).

10 Execution order

Execution of a C# program proceeds such that the side effects of each executing thread are preserved at critical execution points. A side effect is defined as a read or write of a volatile field, a write to a non-volatile variable, a write to an external resource, and the throwing of an exception. The critical execution points at which the order of these side effects must be preserved are references to volatile fields (§10.5.3), lock statements (§8.12), and thread creation and termination. The execution environment is free to change the order of execution of a C# program, subject to the following constraints:

Data dependence is preserved within a thread of execution. That is, the value of each variable is computed as if all statements in the thread were executed in original program order.

Initialization ordering rules are preserved (§10.5.4 and §10.5.5).

The ordering of side effects is preserved with respect to volatile reads and writes (§10.5.3). Additionally, the execution environment need not evaluate part of an expression if it can deduce that that expression’s value is not used and that no needed side effects are produced (including any caused by calling a method or accessing a volatile field). When program execution is interrupted by an asynchronous event (such as an exception thrown by another thread), it is not guaranteed that the observable side effects are visible in the original program order.

Types

The types of the C# language are divided into two main categories: Value types and reference types. Both value types and reference types may be generic types, which take one or more type parameters. Type parameters can designate both value types and reference types.

type: value-type reference-type type-parameter A third category of types, pointers, is available only in unsafe code. This is discussed further in §18.2.

Value types differ from reference types in that variables of the value types directly contain their data, whereas variables of the reference types store references to their data, the latter being known as objects. With reference types, it is possible for two variables to reference the same object, and thus possible for operations on one variable to affect the object referenced by the other variable. With value types, the variables each have their own copy of the data, and it is not possible for operations on one to affect the other.

C#’s type system is unified such that a value of any type can be treated as an object. Every type in C# directly or indirectly derives from the object class type, and object is the ultimate base class of all types. Values of reference types are treated as objects simply by viewing the values as type object. Values of value types are treated as objects by performing boxing and unboxing operations (§4.3).

1 Value types

A value type is either a struct type or an enumeration type. C# provides a set of predefined struct types called the simple types. The simple types are identified through reserved words.

value-type: struct-type enum-type

struct-type: type-name simple-type nullable-type simple-type: numeric-type bool

numeric-type: integral-type floating-point-type decimal integral-type: sbyte byte short ushort int uint long ulong char floating-point-type: float double

nullable-type: non-nullable-value-type ?

non-nullable-value-type: type enum-type: type-name Unlike a variable of a reference type, a variable of a value type can contain the value null only if the value type is a nullable type. For every non-nullable value type there is a corresponding nullable value type denoting the same set of values plus the value null.

Assignment to a variable of a value type creates a copy of the value being assigned. This differs from assignment to a variable of a reference type, which copies the reference but not the object identified by the reference.

1 The System.ValueType type

All value types implicitly inherit from the class System.ValueType, which, in turn, inherits from class object. It is not possible for any type to derive from a value type, and value types are thus implicitly sealed (§10.1.1.2).

Note that System.ValueType is not itself a value-type. Rather, it is a class-type from which all value-types are automatically derived.

2 Default constructors

All value types implicitly declare a public parameterless instance constructor called the default constructor. The default constructor returns a zero-initialized instance known as the default value for the value type:

For all simple-types, the default value is the value produced by a bit pattern of all zeros:

For sbyte, byte, short, ushort, int, uint, long, and ulong, the default value is 0.

For char, the default value is '\x0000'.

For float, the default value is 0.0f.

For double, the default value is 0.0d.

For decimal, the default value is 0.0m.

For bool, the default value is false.

For an enum-type E, the default value is 0, converted to the type E.

For a struct-type, the default value is the value produced by setting all value type fields to their default value and all reference type fields to null.

For a nullable-type the default value is an instance for which the HasValue property is false and the Value property is undefined. The default value is also known as the null value of the nullable type.

Like any other instance constructor, the default constructor of a value type is invoked using the new operator. For efficiency reasons, this requirement is not intended to actually have the implementation generate a constructor call. In the example below, variables i and j are both initialized to zero.

class A
{
void F() { int i = 0; int j = new int(); }
}

Because every value type implicitly has a public parameterless instance constructor, it is not possible for a struct type to contain an explicit declaration of a parameterless constructor. A struct type is however permitted to declare parameterized instance constructors (§11.3.8).

3 Struct types

A struct type is a value type that can declare constants, fields, methods, properties, indexers, operators, instance constructors, static constructors, and nested types. The declaration of struct types is described in §11.1.

4 Simple types

C# provides a set of predefined struct types called the simple types. The simple types are identified through reserved words, but these reserved words are simply aliases for predefined struct types in the System namespace, as described in the table below.

|Reserved word |Aliased type |
|sbyte |System.SByte |
|byte |System.Byte |
|short |System.Int16 |
|ushort |System.UInt16 |
|int |System.Int32 |
|uint |System.UInt32 |
|long |System.Int64 |
|ulong |System.UInt64 |
|char |System.Char |
|float |System.Single |
|double |System.Double |
|bool |System.Boolean |
|decimal |System.Decimal |

Because a simple type aliases a struct type, every simple type has members. For example, int has the members declared in System.Int32 and the members inherited from System.Object, and the following statements are permitted:

int i = int.MaxValue; // System.Int32.MaxValue constant string s = i.ToString(); // System.Int32.ToString() instance method string t = 123.ToString(); // System.Int32.ToString() instance method

The simple types differ from other struct types in that they permit certain additional operations:

Most simple types permit values to be created by writing literals (§2.4.4). For example, 123 is a literal of type int and 'a' is a literal of type char. C# makes no provision for literals of struct types in general, and non-default values of other struct types are ultimately always created through instance constructors of those struct types.

When the operands of an expression are all simple type constants, it is possible for the compiler to evaluate the expression at compile-time. Such an expression is known as a constant-expression (§7.19). Expressions involving operators defined by other struct types are not considered to be constant expressions.

Through const declarations it is possible to declare constants of the simple types (§10.4). It is not possible to have constants of other struct types, but a similar effect is provided by static readonly fields.

Conversions involving simple types can participate in evaluation of conversion operators defined by other struct types, but a user-defined conversion operator can never participate in evaluation of another user-defined operator (§6.4.3).

5 Integral types

C# supports nine integral types: sbyte, byte, short, ushort, int, uint, long, ulong, and char. The integral types have the following sizes and ranges of values:

The sbyte type represents signed 8-bit integers with values between –128 and 127.

The byte type represents unsigned 8-bit integers with values between 0 and 255.

The short type represents signed 16-bit integers with values between –32768 and 32767.

The ushort type represents unsigned 16-bit integers with values between 0 and 65535.

The int type represents signed 32-bit integers with values between –2147483648 and 2147483647.

The uint type represents unsigned 32-bit integers with values between 0 and 4294967295.

The long type represents signed 64-bit integers with values between –9223372036854775808 and 9223372036854775807.

The ulong type represents unsigned 64-bit integers with values between 0 and 18446744073709551615.

The char type represents unsigned 16-bit integers with values between 0 and 65535. The set of possible values for the char type corresponds to the Unicode character set. Although char has the same representation as ushort, not all operations permitted on one type are permitted on the other.

The integral-type unary and binary operators always operate with signed 32-bit precision, unsigned 32-bit precision, signed 64-bit precision, or unsigned 64-bit precision:

For the unary + and ~ operators, the operand is converted to type T, where T is the first of int, uint, long, and ulong that can fully represent all possible values of the operand. The operation is then performed using the precision of type T, and the type of the result is T.

For the unary – operator, the operand is converted to type T, where T is the first of int and long that can fully represent all possible values of the operand. The operation is then performed using the precision of type T, and the type of the result is T. The unary – operator cannot be applied to operands of type ulong.

For the binary +, –, *, /, %, &, ^, |, ==, !=, >, =, and operators, the left operand is converted to type T, where T is the first of int, uint, long, and ulong that can fully represent all possible values of the operand. The operation is then performed using the precision of type T, and the type of the result is T.

The char type is classified as an integral type, but it differs from the other integral types in two ways:

There are no implicit conversions from other types to the char type. In particular, even though the sbyte, byte, and ushort types have ranges of values that are fully representable using the char type, implicit conversions from sbyte, byte, or ushort to char do not exist.

Constants of the char type must be written as character-literals or as integer-literals in combination with a cast to type char. For example, (char)10 is the same as '\x000A'.

The checked and unchecked operators and statements are used to control overflow checking for integral-type arithmetic operations and conversions (§7.6.12). In a checked context, an overflow produces a compile-time error or causes a System.OverflowException to be thrown. In an unchecked context, overflows are ignored and any high-order bits that do not fit in the destination type are discarded.

6 Floating point types

C# supports two floating point types: float and double. The float and double types are represented using the 32-bit single-precision and 64-bit double-precision IEEE 754 formats, which provide the following sets of values:

Positive zero and negative zero. In most situations, positive zero and negative zero behave identically as the simple value zero, but certain operations distinguish between the two (§7.8.2).

Positive infinity and negative infinity. Infinities are produced by such operations as dividing a non-zero number by zero. For example, 1.0 / 0.0 yields positive infinity, and –1.0 / 0.0 yields negative infinity.

The Not-a-Number value, often abbreviated NaN. NaNs are produced by invalid floating-point operations, such as dividing zero by zero.

The finite set of non-zero values of the form s × m × 2e, where s is 1 or −1, and m and e are determined by the particular floating-point type: For float, 0 < m < 224 and −149 ≤ e ≤ 104, and for double, 0 < m < 253 and −1075 ≤ e ≤ 970. Denormalized floating-point numbers are considered valid non-zero values.

The float type can represent values ranging from approximately 1.5 × 10−45 to 3.4 × 1038 with a precision of 7 digits.

The double type can represent values ranging from approximately 5.0 × 10−324 to 1.7 × 10308 with a precision of 15-16 digits.

If one of the operands of a binary operator is of a floating-point type, then the other operand must be of an integral type or a floating-point type, and the operation is evaluated as follows:

If one of the operands is of an integral type, then that operand is converted to the floating-point type of the other operand.

Then, if either of the operands is of type double, the other operand is converted to double, the operation is performed using at least double range and precision, and the type of the result is double (or bool for the relational operators).

Otherwise, the operation is performed using at least float range and precision, and the type of the result is float (or bool for the relational operators).

The floating-point operators, including the assignment operators, never produce exceptions. Instead, in exceptional situations, floating-point operations produce zero, infinity, or NaN, as described below:

If the result of a floating-point operation is too small for the destination format, the result of the operation becomes positive zero or negative zero.

If the result of a floating-point operation is too large for the destination format, the result of the operation becomes positive infinity or negative infinity.

If a floating-point operation is invalid, the result of the operation becomes NaN.

If one or both operands of a floating-point operation is NaN, the result of the operation becomes NaN.

Floating-point operations may be performed with higher precision than the result type of the operation. For example, some hardware architectures support an “extended” or “long double” floating-point type with greater range and precision than the double type, and implicitly perform all floating-point operations using this higher precision type. Only at excessive cost in performance can such hardware architectures be made to perform floating-point operations with less precision, and rather than require an implementation to forfeit both performance and precision, C# allows a higher precision type to be used for all floating-point operations. Other than delivering more precise results, this rarely has any measurable effects. However, in expressions of the form x * y / z, where the multiplication produces a result that is outside the double range, but the subsequent division brings the temporary result back into the double range, the fact that the expression is evaluated in a higher range format may cause a finite result to be produced instead of an infinity.

7 The decimal type

The decimal type is a 128-bit data type suitable for financial and monetary calculations. The decimal type can represent values ranging from 1.0 × 10−28 to approximately 7.9 × 1028 with 28-29 significant digits.

The finite set of values of type decimal are of the form (–1)s × c × 10-e, where the sign s is 0 or 1, the coefficient c is given by 0 ≤ c operator may be used to access a member of a struct through a pointer (§18.5.2).

The [] operator may be used to index a pointer (§18.5.3).

The & operator may be used to obtain the address of a variable (§18.5.4).

The ++ and -- operators may be used to increment and decrement pointers (§18.5.5).

The + and - operators may be used to perform pointer arithmetic (§18.5.6).

The ==, !=, , operators may be used to compare pointers (§18.5.7).

The stackalloc operator may be used to allocate memory from the call stack (§18.7).

The fixed statement may be used to temporarily fix a variable so its address can be obtained (§18.6).

3 Fixed and moveable variables

The address-of operator (§18.5.4) and the fixed statement (§18.6) divide variables into two categories: Fixed variables and moveable variables.

Fixed variables reside in storage locations that are unaffected by operation of the garbage collector. (Examples of fixed variables include local variables, value parameters, and variables created by dereferencing pointers.) On the other hand, moveable variables reside in storage locations that are subject to relocation or disposal by the garbage collector. (Examples of moveable variables include fields in objects and elements of arrays.)

The & operator (§18.5.4) permits the address of a fixed variable to be obtained without restrictions. However, because a moveable variable is subject to relocation or disposal by the garbage collector, the address of a moveable variable can only be obtained using a fixed statement (§18.6), and that address remains valid only for the duration of that fixed statement.

In precise terms, a fixed variable is one of the following:

A variable resulting from a simple-name (§7.6.2) that refers to a local variable or a value parameter, unless the variable is captured by an anonymous function.

A variable resulting from a member-access (§7.6.4) of the form V.I, where V is a fixed variable of a struct-type.

A variable resulting from a pointer-indirection-expression (§18.5.1) of the form *P, a pointer-member-access (§18.5.2) of the form P->I, or a pointer-element-access (§18.5.3) of the form P[E].

All other variables are classified as moveable variables.

Note that a static field is classified as a moveable variable. Also note that a ref or out parameter is classified as a moveable variable, even if the argument given for the parameter is a fixed variable. Finally, note that a variable produced by dereferencing a pointer is always classified as a fixed variable.

4 Pointer conversions

In an unsafe context, the set of available implicit conversions (§6.1) is extended to include the following implicit pointer conversions:

From any pointer-type to the type void*.

From the null literal to any pointer-type.

Additionally, in an unsafe context, the set of available explicit conversions (§6.2) is extended to include the following explicit pointer conversions:

From any pointer-type to any other pointer-type.

From sbyte, byte, short, ushort, int, uint, long, or ulong to any pointer-type.

From any pointer-type to sbyte, byte, short, ushort, int, uint, long, or ulong.

Finally, in an unsafe context, the set of standard implicit conversions (§6.3.1) includes the following pointer conversion:

From any pointer-type to the type void*.

Conversions between two pointer types never change the actual pointer value. In other words, a conversion from one pointer type to another has no effect on the underlying address given by the pointer.

When one pointer type is converted to another, if the resulting pointer is not correctly aligned for the pointed-to type, the behavior is undefined if the result is dereferenced. In general, the concept “correctly aligned” is transitive: if a pointer to type A is correctly aligned for a pointer to type B, which, in turn, is correctly aligned for a pointer to type C, then a pointer to type A is correctly aligned for a pointer to type C.

Consider the following case in which a variable having one type is accessed via a pointer to a different type:

char c = 'A'; char* pc = &c; void* pv = pc; int* pi = (int*)pv; int i = *pi; // undefined
*pi = 123456; // undefined

When a pointer type is converted to a pointer to byte, the result points to the lowest addressed byte of the variable. Successive increments of the result, up to the size of the variable, yield pointers to the remaining bytes of that variable. For example, the following method displays each of the eight bytes in a double as a hexadecimal value:

using System;

class Test
{
unsafe static void Main() { double d = 123.456e23; unsafe { byte* pb = (byte*)&d; for (int i = 0; i < sizeof(double); ++i) Console.Write("{0:X2} ", *pb++); Console.WriteLine(); } }
}

Of course, the output produced depends on endianness.

Mappings between pointers and integers are implementation-defined. However, on 32- and 64-bit CPU architectures with a linear address space, conversions of pointers to or from integral types typically behave exactly like conversions of uint or ulong values, respectively, to or from those integral types.

1 Pointer arrays

In an unsafe context, arrays of pointers can be constructed. Only some of the conversions that apply to other array types are allowed on pointer arrays:

The implicit reference conversion (§6.1.6) from any array-type to System.Array and the interfaces it implements also applies to pointer arrays. However, any attempt to access the array elements through System.Array or the interfaces it implements will result in an exception at run-time, as pointer types are not convertible to object.

The implicit and explicit reference conversions (§6.1.6, §6.2.4) from a single-dimensional array type S[] to System.Collections.Generic.IList and its base interfaces never apply to pointer arrays, since pointer types cannot be used as type arguments, and there are no conversions from pointer types to non-pointer types.

The explicit reference conversion (§6.2.4) from System.Array and the interfaces it implements to any array-type applies to pointer arrays.

The explicit reference conversions (§6.2.4) from System.Collections.Generic.IList and its base interfaces to a single-dimensional array type T[] never applies to pointer arrays, since pointer types cannot be used as type arguments, and there are no conversions from pointer types to non-pointer types.

These restrictions mean that the expansion for the foreach statement over arrays described in §8.8.4 cannot be applied to pointer arrays. Instead, a foreach statement of the form

foreach (V v in x) embedded-statement

where the type of x is an array type of the form T[,,…,], n is the number of dimensions minus 1 and T or V is a pointer type, is expanded using nested for-loops as follows:

{ T[,,…,] a = x; V v; for (int i0 = a.GetLowerBound(0); i0 I, P must be an expression of a pointer type other than void*, and I must denote an accessible member of the type to which P points.

A pointer member access of the form P->I is evaluated exactly as (*P).I. For a description of the pointer indirection operator (*), see §18.5.1. For a description of the member access operator (.), see §7.6.4.

In the example

using System;

struct Point
{
public int x; public int y;

public override string ToString() { return "(" + x + "," + y + ")"; }
}

class Test
{
static void Main() { Point point; unsafe { Point* p = &point; p->x = 10; p->y = 20; Console.WriteLine(p->ToString()); } }
}

the -> operator is used to access fields and invoke a method of a struct through a pointer. Because the operation P->I is precisely equivalent to (*P).I, the Main method could equally well have been written:

class Test
{
static void Main() { Point point; unsafe { Point* p = &point; (*p).x = 10; (*p).y = 20; Console.WriteLine((*p).ToString()); } }
}

3 Pointer element access

A pointer-element-access consists of a primary-no-array-creation-expression followed by an expression enclosed in “[” and “]”.

pointer-element-access: primary-no-array-creation-expression [ expression ]

In a pointer element access of the form P[E], P must be an expression of a pointer type other than void*, and E must be an expression that can be implicitly converted to int, uint, long, or ulong.

A pointer element access of the form P[E] is evaluated exactly as *(P + E). For a description of the pointer indirection operator (*), see §18.5.1. For a description of the pointer addition operator (+), see §18.5.6.

In the example

class Test
{
static void Main() { unsafe { char* p = stackalloc char[256]; for (int i = 0; i < 256; i++) p[i] = (char)i; } }
}

a pointer element access is used to initialize the character buffer in a for loop. Because the operation P[E] is precisely equivalent to *(P + E), the example could equally well have been written:

class Test
{
static void Main() { unsafe { char* p = stackalloc char[256]; for (int i = 0; i < 256; i++) *(p + i) = (char)i; } }
}

The pointer element access operator does not check for out-of-bounds errors and the behavior when accessing an out-of-bounds element is undefined. This is the same as C and C++.

4 The address-of operator

An addressof-expression consists of an ampersand (&) followed by a unary-expression.

addressof-expression:
& unary-expression

Given an expression E which is of a type T and is classified as a fixed variable (§18.3), the construct &E computes the address of the variable given by E. The type of the result is T* and is classified as a value. A compile-time error occurs if E is not classified as a variable, if E is classified as a read-only local variable, or if E denotes a moveable variable. In the last case, a fixed statement (§18.6) can be used to temporarily “fix” the variable before obtaining its address. As stated in §7.6.4, outside an instance constructor or static constructor for a struct or class that defines a readonly field, that field is considered a value, not a variable. As such, its address cannot be taken. Similarly, the address of a constant cannot be taken.

The & operator does not require its argument to be definitely assigned, but following an & operation, the variable to which the operator is applied is considered definitely assigned in the execution path in which the operation occurs. It is the responsibility of the programmer to ensure that correct initialization of the variable actually does take place in this situation.

In the example

using System;

class Test
{
static void Main() { int i; unsafe { int* p = &i; *p = 123; } Console.WriteLine(i); }
}

i is considered definitely assigned following the &i operation used to initialize p. The assignment to *p in effect initializes i, but the inclusion of this initialization is the responsibility of the programmer, and no compile-time error would occur if the assignment was removed.

The rules of definite assignment for the & operator exist such that redundant initialization of local variables can be avoided. For example, many external APIs take a pointer to a structure which is filled in by the API. Calls to such APIs typically pass the address of a local struct variable, and without the rule, redundant initialization of the struct variable would be required.

5 Pointer increment and decrement

In an unsafe context, the ++ and -- operators (§7.6.9 and §7.7.5) can be applied to pointer variables of all types except void*. Thus, for every pointer type T*, the following operators are implicitly defined:

T* operator ++(T* x);

T* operator --(T* x);

The operators produce the same results as x + 1 and x - 1, respectively (§18.5.6). In other words, for a pointer variable of type T*, the ++ operator adds sizeof(T) to the address contained in the variable, and the -- operator subtracts sizeof(T) from the address contained in the variable.

If a pointer increment or decrement operation overflows the domain of the pointer type, the result is implementation-defined, but no exceptions are produced.

6 Pointer arithmetic

In an unsafe context, the + and - operators (§7.8.4 and §7.8.5) can be applied to values of all pointer types except void*. Thus, for every pointer type T*, the following operators are implicitly defined:

T* operator +(T* x, int y);
T* operator +(T* x, uint y);
T* operator +(T* x, long y);
T* operator +(T* x, ulong y);

T* operator +(int x, T* y);
T* operator +(uint x, T* y);
T* operator +(long x, T* y);
T* operator +(ulong x, T* y);

T* operator –(T* x, int y);
T* operator –(T* x, uint y);
T* operator –(T* x, long y);
T* operator –(T* x, ulong y);

long operator –(T* x, T* y);

Given an expression P of a pointer type T* and an expression N of type int, uint, long, or ulong, the expressions P + N and N + P compute the pointer value of type T* that results from adding N * sizeof(T) to the address given by P. Likewise, the expression P - N computes the pointer value of type T* that results from subtracting N * sizeof(T) from the address given by P.

Given two expressions, P and Q, of a pointer type T*, the expression P – Q computes the difference between the addresses given by P and Q and then divides that difference by sizeof(T). The type of the result is always long. In effect, P - Q is computed as ((long)(P) - (long)(Q)) / sizeof(T).

For example:

using System;

class Test
{

static void Main() { unsafe { int* values = stackalloc int[20]; int* p = &values[1]; int* q = &values[15]; Console.WriteLine("p - q = {0}", p - q); Console.WriteLine("q - p = {0}", q - p); } }
}

which produces the output:

p - q = -14 q - p = 14

If a pointer arithmetic operation overflows the domain of the pointer type, the result is truncated in an implementation-defined fashion, but no exceptions are produced.

7 Pointer comparison

In an unsafe context, the ==, !=, , operators (§7.10) can be applied to values of all pointer types. The pointer comparison operators are:

bool operator ==(void* x, void* y);

bool operator !=(void* x, void* y);

bool operator (void* x, void* y);

bool operator =(void* x, void* y);

Because an implicit conversion exists from any pointer type to the void* type, operands of any pointer type can be compared using these operators. The comparison operators compare the addresses given by the two operands as if they were unsigned integers.

8 The sizeof operator

The sizeof operator returns the number of bytes occupied by a variable of a given type. The type specified as an operand to sizeof must be an unmanaged-type (§18.2).

sizeof-expression: sizeof ( unmanaged-type )

The result of the sizeof operator is a value of type int. For certain predefined types, the sizeof operator yields a constant value as shown in the table below.

|Expression |Result |
|sizeof(sbyte) |1 |
|sizeof(byte) |1 |
|sizeof(short) |2 |
|sizeof(ushort) |2 |
|sizeof(int) |4 |
|sizeof(uint) |4 |
|sizeof(long) |8 |
|sizeof(ulong) |8 |
|sizeof(char) |2 |
|sizeof(float) |4 |
|sizeof(double) |8 |
|sizeof(bool) |1 |

For all other types, the result of the sizeof operator is implementation-defined and is classified as a value, not a constant.

The order in which members are packed into a struct is unspecified.

For alignment purposes, there may be unnamed padding at the beginning of a struct, within a struct, and at the end of the struct. The contents of the bits used as padding are indeterminate.

When applied to an operand that has struct type, the result is the total number of bytes in a variable of that type, including any padding.

6 The fixed statement

In an unsafe context, the embedded-statement (§8) production permits an additional construct, the fixed statement, which is used to “fix” a moveable variable such that its address remains constant for the duration of the statement.

embedded-statement:
...
fixed-statement

fixed-statement: fixed ( pointer-type fixed-pointer-declarators ) embedded-statement

fixed-pointer-declarators: fixed-pointer-declarator fixed-pointer-declarators , fixed-pointer-declarator

fixed-pointer-declarator: identifier = fixed-pointer-initializer

fixed-pointer-initializer:
& variable-reference expression Each fixed-pointer-declarator declares a local variable of the given pointer-type and initializes that local variable with the address computed by the corresponding fixed-pointer-initializer. A local variable declared in a fixed statement is accessible in any fixed-pointer-initializers occurring to the right of that variable’s declaration, and in the embedded-statement of the fixed statement. A local variable declared by a fixed statement is considered read-only. A compile-time error occurs if the embedded statement attempts to modify this local variable (via assignment or the ++ and -- operators) or pass it as a ref or out parameter.

A fixed-pointer-initializer can be one of the following:

The token “&” followed by a variable-reference (§5.3.3) to a moveable variable (§18.3) of an unmanaged type T, provided the type T* is implicitly convertible to the pointer type given in the fixed statement. In this case, the initializer computes the address of the given variable, and the variable is guaranteed to remain at a fixed address for the duration of the fixed statement.

An expression of an array-type with elements of an unmanaged type T, provided the type T* is implicitly convertible to the pointer type given in the fixed statement. In this case, the initializer computes the address of the first element in the array, and the entire array is guaranteed to remain at a fixed address for the duration of the fixed statement. The behavior of the fixed statement is implementation-defined if the array expression is null or if the array has zero elements.

An expression of type string, provided the type char* is implicitly convertible to the pointer type given in the fixed statement. In this case, the initializer computes the address of the first character in the string, and the entire string is guaranteed to remain at a fixed address for the duration of the fixed statement. The behavior of the fixed statement is implementation-defined if the string expression is null.

A simple-name or member-access that references a fixed size buffer member of a moveable variable, provided the type of the fixed size buffer member is implicitly convertible to the pointer type given in the fixed statement. In this case, the initializer computes a pointer to the first element of the fixed size buffer (§18.7.2), and the fixed size buffer is guaranteed to remain at a fixed address for the duration of the fixed statement.

For each address computed by a fixed-pointer-initializer the fixed statement ensures that the variable referenced by the address is not subject to relocation or disposal by the garbage collector for the duration of the fixed statement. For example, if the address computed by a fixed-pointer-initializer references a field of an object or an element of an array instance, the fixed statement guarantees that the containing object instance is not relocated or disposed of during the lifetime of the statement.

It is the programmer’s responsibility to ensure that pointers created by fixed statements do not survive beyond execution of those statements. For example, when pointers created by fixed statements are passed to external APIs, it is the programmer’s responsibility to ensure that the APIs retain no memory of these pointers.

Fixed objects may cause fragmentation of the heap (because they can’t be moved). For that reason, objects should be fixed only when absolutely necessary and then only for the shortest amount of time possible.

The example

class Test
{
static int x; int y;

unsafe static void F(int* p) { *p = 1; }

static void Main() { Test t = new Test(); int[] a = new int[10]; unsafe { fixed (int* p = &x) F(p); fixed (int* p = &t.y) F(p); fixed (int* p = &a[0]) F(p); fixed (int* p = a) F(p); } }
}

demonstrates several uses of the fixed statement. The first statement fixes and obtains the address of a static field, the second statement fixes and obtains the address of an instance field, and the third statement fixes and obtains the address of an array element. In each case it would have been an error to use the regular & operator since the variables are all classified as moveable variables.

The fourth fixed statement in the example above produces a similar result to the third.

This example of the fixed statement uses string:

class Test
{
static string name = "xx";

unsafe static void F(char* p) { for (int i = 0; p[i] != '\0'; ++i) Console.WriteLine(p[i]); }

static void Main() { unsafe { fixed (char* p = name) F(p); fixed (char* p = "xx") F(p); } }
}

In an unsafe context array elements of single-dimensional arrays are stored in increasing index order, starting with index 0 and ending with index Length – 1. For multi-dimensional arrays, array elements are stored such that the indices of the rightmost dimension are increased first, then the next left dimension, and so on to the left. Within a fixed statement that obtains a pointer p to an array instance a, the pointer values ranging from p to p + a.Length - 1 represent addresses of the elements in the array. Likewise, the variables ranging from p[0] to p[a.Length - 1] represent the actual array elements. Given the way in which arrays are stored, we can treat an array of any dimension as though it were linear.

For example:

using System;

class Test
{
static void Main() { int[,,] a = new int[2,3,4]; unsafe { fixed (int* p = a) { for (int i = 0; i < a.Length; ++i) // treat as linear p[i] = i; } }

for (int i = 0; i < 2; ++i) for (int j = 0; j < 3; ++j) { for (int k = 0; k < 4; ++k) Console.Write("[{0},{1},{2}] = {3,2} ", i, j, k, a[i,j,k]); Console.WriteLine(); } }
}

which produces the output:

[0,0,0] = 0 [0,0,1] = 1 [0,0,2] = 2 [0,0,3] = 3
[0,1,0] = 4 [0,1,1] = 5 [0,1,2] = 6 [0,1,3] = 7
[0,2,0] = 8 [0,2,1] = 9 [0,2,2] = 10 [0,2,3] = 11
[1,0,0] = 12 [1,0,1] = 13 [1,0,2] = 14 [1,0,3] = 15
[1,1,0] = 16 [1,1,1] = 17 [1,1,2] = 18 [1,1,3] = 19
[1,2,0] = 20 [1,2,1] = 21 [1,2,2] = 22 [1,2,3] = 23

In the example

class Test
{
unsafe static void Fill(int* p, int count, int value) { for (; count != 0; count--) *p++ = value; }

static void Main() { int[] a = new int[100]; unsafe { fixed (int* p = a) Fill(p, 100, -1); } }
}

a fixed statement is used to fix an array so its address can be passed to a method that takes a pointer.

In the example:

unsafe struct Font
{
public int size; public fixed char name[32];
}

class Test
{
unsafe static void PutString(string s, char* buffer, int bufSize) { int len = s.Length; if (len > bufSize) len = bufSize; for (int i = 0; i < len; i++) buffer[i] = s[i]; for (int i = len; i < bufSize; i++) buffer[i] = (char)0; }

Font f;

unsafe static void Main() { Test test = new Test(); test.f.size = 10; fixed (char* p = test.f.name) { PutString("Times New Roman", p, 32); } }
}

a fixed statement is used to fix a fixed size buffer of a struct so its address can be used as a pointer.

A char* value produced by fixing a string instance always points to a null-terminated string. Within a fixed statement that obtains a pointer p to a string instance s, the pointer values ranging from p to p + s.Length - 1 represent addresses of the characters in the string, and the pointer value p + s.Length always points to a null character (the character with value '\0').

Modifying objects of managed type through fixed pointers can results in undefined behavior. For example, because strings are immutable, it is the programmer’s responsibility to ensure that the characters referenced by a pointer to a fixed string are not modified.

The automatic null-termination of strings is particularly convenient when calling external APIs that expect “C-style” strings. Note, however, that a string instance is permitted to contain null characters. If such null characters are present, the string will appear truncated when treated as a null-terminated char*.

7 Fixed size buffers

Fixed size buffers are used to declare “C style” in-line arrays as members of structs, and are primarily useful for interfacing with unmanaged APIs.

1 Fixed size buffer declarations

A fixed size buffer is a member that represents storage for a fixed length buffer of variables of a given type. A fixed size buffer declaration introduces one or more fixed size buffers of a given element type. Fixed size buffers are only permitted in struct declarations and can only occur in unsafe contexts (§18.1).

struct-member-declaration:
…
fixed-size-buffer-declaration

fixed-size-buffer-declaration: attributesopt fixed-size-buffer-modifiersopt fixed buffer-element-type fixed-size-buffer-declarators ;

fixed-size-buffer-modifiers: fixed-size-buffer-modifier fixed-size-buffer-modifier fixed-size-buffer-modifiers

fixed-size-buffer-modifier: new public protected internal private unsafe

buffer-element-type: type fixed-size-buffer-declarators: fixed-size-buffer-declarator fixed-size-buffer-declarator , fixed-size-buffer-declarators

fixed-size-buffer-declarator: identifier [ constant-expression ]

A fixed size buffer declaration may include a set of attributes (§17), a new modifier (§10.2.2), a valid combination of the four access modifiers (§10.2.3) and an unsafe modifier (§18.1). The attributes and modifiers apply to all of the members declared by the fixed size buffer declaration. It is an error for the same modifier to appear multiple times in a fixed size buffer declaration.

A fixed size buffer declaration is not permitted to include the static modifier.

The buffer element type of a fixed size buffer declaration specifies the element type of the buffer(s) introduced by the declaration. The buffer element type must be one of the predefined types sbyte, byte, short, ushort, int, uint, long, ulong, char, float, double, or bool.

The buffer element type is followed by a list of fixed size buffer declarators, each of which introduces a new member. A fixed size buffer declarator consists of an identifier that names the member, followed by a constant expression enclosed in [ and ] tokens. The constant expression denotes the number of elements in the member introduced by that fixed size buffer declarator. The type of the constant expression must be implicitly convertible to type int, and the value must be a non-zero positive integer.

The elements of a fixed size buffer are guaranteed to be laid out sequentially in memory.

A fixed size buffer declaration that declares multiple fixed size buffers is equivalent to multiple declarations of a single fixed size buffer declation with the same attributes, and element types. For example

unsafe struct A
{
public fixed int x[5], y[10], z[100];
}

is equivalent to

unsafe struct A
{
public fixed int x[5]; public fixed int y[10]; public fixed int z[100];
}

2 Fixed size buffers in expressions

Member lookup (§7.3) of a fixed size buffer member proceeds exactly like member lookup of a field.

A fixed size buffer can be referenced in an expression using a simple-name (§7.5.2) or a member-access (§7.5.4).

When a fixed size buffer member is referenced as a simple name, the effect is the same as a member access of the form this.I, where I is the fixed size buffer member.

In a member access of the form E.I, if E is of a struct type and a member lookup of I in that struct type identifies a fixed size member, then E.I is evaluated an classified as follows:

If the expression E.I does not occur in an unsafe context, a compile-time error occurs.

If E is classified as a value, a compile-time error occurs.

Otherwise, if E is a moveable variable (§18.3) and the expression E.I is not a fixed-pointer-initializer (§18.6), a compile-time error occurs.

Otherwise, E references a fixed variable and the result of the expression is a pointer to the first element of the fixed size buffer member I in E. The result is of type S*, where S is the element type of I, and is classified as a value.

The subsequent elements of the fixed size buffer can be accessed using pointer operations from the first element. Unlike access to arrays, access to the elements of a fixed size buffer is an unsafe operation and is not range checked.

The following example declares and uses a struct with a fixed size buffer member.

unsafe struct Font
{
public int size; public fixed char name[32];
}

class Test
{
unsafe static void PutString(string s, char* buffer, int bufSize) { int len = s.Length; if (len > bufSize) len = bufSize; for (int i = 0; i < len; i++) buffer[i] = s[i]; for (int i = len; i < bufSize; i++) buffer[i] = (char)0; }

unsafe static void Main() { Font f; f.size = 10; PutString("Times New Roman", f.name, 32); }
}

3 Definite assignment checking

Fixed size buffers are not subject to definite assignment checking (§5.3), and fixed size buffer members are ignored for purposes of definite assignment checking of struct type variables.

When the outermost containing struct variable of a fixed size buffer member is a static variable, an instance variable of a class instance, or an array element, the elements of the fixed size buffer are automatically initialized to their default values (§5.2). In all other cases, the initial content of a fixed size buffer is undefined.

8 Stack allocation

In an unsafe context, a local variable declaration (§8.5.1) may include a stack allocation initializer which allocates memory from the call stack.

local-variable-initializer:
…
stackalloc-initializer

stackalloc-initializer: stackalloc unmanaged-type [ expression ]

The unmanaged-type indicates the type of the items that will be stored in the newly allocated location, and the expression indicates the number of these items. Taken together, these specify the required allocation size. Since the size of a stack allocation cannot be negative, it is a compile-time error to specify the number of items as a constant-expression that evaluates to a negative value.

A stack allocation initializer of the form stackalloc T[E] requires T to be an unmanaged type (§18.2) and E to be an expression of type int. The construct allocates E * sizeof(T) bytes from the call stack and returns a pointer, of type T*, to the newly allocated block. If E is a negative value, then the behavior is undefined. If E is zero, then no allocation is made, and the pointer returned is implementation-defined. If there is not enough memory available to allocate a block of the given size, a System.StackOverflowException is thrown.

The content of the newly allocated memory is undefined.

Stack allocation initializers are not permitted in catch or finally blocks (§8.10).

There is no way to explicitly free memory allocated using stackalloc. All stack allocated memory blocks created during the execution of a function member are automatically discarded when that function member returns. This corresponds to the alloca function, an extension commonly found in C and C++ implementations.

In the example

using System;

class Test
{
static string IntToString(int value) { int n = value >= 0? value: -value; unsafe { char* buffer = stackalloc char[16]; char* p = buffer + 16; do { *--p = (char)(n % 10 + '0'); n /= 10; } while (n != 0); if (value < 0) *--p = '-'; return new string(p, 0, (int)(buffer + 16 - p)); } }

static void Main() { Console.WriteLine(IntToString(12345)); Console.WriteLine(IntToString(-999)); }
}

a stackalloc initializer is used in the IntToString method to allocate a buffer of 16 characters on the stack. The buffer is automatically discarded when the method returns.

9 Dynamic memory allocation

Except for the stackalloc operator, C# provides no predefined constructs for managing non-garbage collected memory. Such services are typically provided by supporting class libraries or imported directly from the underlying operating system. For example, the Memory class below illustrates how the heap functions of an underlying operating system might be accessed from C#:

using System; using System.Runtime.InteropServices;

public unsafe class Memory
{
// Handle for the process heap. This handle is used in all calls to the // HeapXXX APIs in the methods below.

static int ph = GetProcessHeap();

// Private instance constructor to prevent instantiation.

private Memory() {}

// Allocates a memory block of the given size. The allocated memory is // automatically initialized to zero.

public static void* Alloc(int size) { void* result = HeapAlloc(ph, HEAP_ZERO_MEMORY, size); if (result == null) throw new OutOfMemoryException(); return result; }

// Copies count bytes from src to dst. The source and destination // blocks are permitted to overlap.

public static void Copy(void* src, void* dst, int count) { byte* ps = (byte*)src; byte* pd = (byte*)dst; if (ps > pd) { for (; count != 0; count--) *pd++ = *ps++; } else if (ps < pd) { for (ps += count, pd += count; count != 0; count--) *--pd = *--ps; } }

// Frees a memory block.

public static void Free(void* block) { if (!HeapFree(ph, 0, block)) throw new InvalidOperationException(); }

// Re-allocates a memory block. If the reallocation request is for a // larger size, the additional region of memory is automatically // initialized to zero.

public static void* ReAlloc(void* block, int size) { void* result = HeapReAlloc(ph, HEAP_ZERO_MEMORY, block, size); if (result == null) throw new OutOfMemoryException(); return result; }

// Returns the size of a memory block.

public static int SizeOf(void* block) { int result = HeapSize(ph, 0, block); if (result == -1) throw new InvalidOperationException(); return result; }

// Heap API flags

const int HEAP_ZERO_MEMORY = 0x00000008;

// Heap API functions

[DllImport("kernel32")] static extern int GetProcessHeap();

[DllImport("kernel32")] static extern void* HeapAlloc(int hHeap, int flags, int size);

[DllImport("kernel32")] static extern bool HeapFree(int hHeap, int flags, void* block);

[DllImport("kernel32")] static extern void* HeapReAlloc(int hHeap, int flags, void* block, int size);

[DllImport("kernel32")] static extern int HeapSize(int hHeap, int flags, void* block);
}

An example that uses the Memory class is given below:

class Test
{
static void Main() { unsafe { byte* buffer = (byte*)Memory.Alloc(256); try { for (int i = 0; i < 256; i++) buffer[i] = (byte)i; byte[] array = new byte[256]; fixed (byte* p = array) Memory.Copy(buffer, p, 256); } finally { Memory.Free(buffer); } for (int i = 0; i < 256; i++) Console.WriteLine(array[i]); } }
}

The example allocates 256 bytes of memory through Memory.Alloc and initializes the memory block with values increasing from 0 to 255. It then allocates a 256 element byte array and uses Memory.Copy to copy the contents of the memory block into the byte array. Finally, the memory block is freed using Memory.Free and the contents of the byte array are output on the console.

Documentation comments

C# provides a mechanism for programmers to document their code using a special comment syntax that contains XML text. In source code files, comments having a certain form can be used to direct a tool to produce XML from those comments and the source code elements, which they precede. Comments using such syntax are called documentation comments. They must immediately precede a user-defined type (such as a class, delegate, or interface) or a member (such as a field, event, property, or method). The XML generation tool is called the documentation generator. (This generator could be, but need not be, the C# compiler itself.) The output produced by the documentation generator is called the documentation file. A documentation file is used as input to a documentation viewer; a tool intended to produce some sort of visual display of type information and its associated documentation.

This specification suggests a set of tags to be used in documentation comments, but use of these tags is not required, and other tags may be used if desired, as long the rules of well-formed XML are followed.

1. Introduction
Comments having a special form can be used to direct a tool to produce XML from those comments and the source code elements, which they precede. Such comments are single-line comments that start with three slashes (///), or delimited comments that start with a slash and two stars (/**). They must immediately precede a user-defined type (such as a class, delegate, or interface) or a member (such as a field, event, property, or method) that they annotate. Attribute sections (§17.2) are considered part of declarations, so documentation comments must precede attributes applied to a type or member.

Syntax:

single-line-doc-comment:
/// input-charactersopt

delimited-doc-comment:
/** delimited-comment-textopt */

In a single-line-doc-comment, if there is a whitespace character following the /// characters on each of the single-line-doc-comments adjacent to the current single-line-doc-comment, then that whitespace character is not included in the XML output.

In a delimited-doc-comment, if the first non-whitespace character on the second line is an asterisk and the same pattern of optional whitespace characters and an asterisk character is repeated at the beginning of each of the line within the delimited-doc-comment, then the characters of the repeated pattern are not included in the XML output. The pattern may include whitespace characters after, as well as before, the asterisk character.

Example:

/// Class Point models a point in a two-dimensional
/// plane.
///
public class Point
{
/// method draw renders the point. void draw() {…}
}

The text within documentation comments must be well formed according to the rules of XML (http://www.w3.org/TR/REC-xml). If the XML is ill formed, a warning is generated and the documentation file will contain a comment saying that an error was encountered.

Although developers are free to create their own set of tags, a recommended set is defined in §A.2. Some of the recommended tags have special meanings:

The tag is used to describe parameters. If such a tag is used, the documentation generator must verify that the specified parameter exists and that all parameters are described in documentation comments. If such verification fails, the documentation generator issues a warning.

The cref attribute can be attached to any tag to provide a reference to a code element. The documentation generator must verify that this code element exists. If the verification fails, the documentation generator issues a warning. When looking for a name described in a cref attribute, the documentation generator must respect namespace visibility according to using statements appearing within the source code. For code elements that are generic, the normal generic syntax (ie “List”) cannot be used because it produces invalid XML. Braces can be used instead of brackets (ie “List{T}”), or the XML escape syntax can be used (ie “List<T>”).

The tag is intended to be used by a documentation viewer to display additional information about a type or member.

The tag includes information from an external XML file.

Note carefully that the documentation file does not provide full information about the type and members (for example, it does not contain any type information). To get such information about a type or member, the documentation file must be used in conjunction with reflection on the actual type or member.

2. Recommended tags
The documentation generator must accept and process any tag that is valid according to the rules of XML. The following tags provide commonly used functionality in user documentation. (Of course, other tags are possible.)

|Tag |Section |Purpose |
| |A.2.1 |Set text in a code-like font |
| |A.2.2 |Set one or more lines of source code or program output |
| |A.2.3 |Indicate an example |
| |A.2.4 |Identifies the exceptions a method can throw |
| |A.2.5 |Includes XML from an external file |
| |A.2.6 |Create a list or table |
| |A.2.7 |Permit structure to be added to text |
| |A.2.8 |Describe a parameter for a method or constructor |
| |A.2.9 |Identify that a word is a parameter name |
| |A.2.10 |Document the security accessibility of a member |
| |A.2.11 |Describe additional information about a type |
| |A.2.12 |Describe the return value of a method |
| |A.2.13 |Specify a link |
| |A.2.14 |Generate a See Also entry |
| |A.2.15 |Describe a type or a member of a type |
| |A.2.16 |Describe a property |
| | |Describe a generic type parameter |
| | |Identify that a word is a type parameter name |

1.
This tag provides a mechanism to indicate that a fragment of text within a description should be set in a special font such as that used for a block of code. For lines of actual code, use (§A.2.2).

Syntax:

text

Example:

/// Class Point models a point in a two-dimensional
/// plane.

public class Point
{
// ...
}

2.
This tag is used to set one or more lines of source code or program output in some special font. For small code fragments in narrative, use (§A.2.1).

Syntax:

source code or program output

Example:

/// This method changes the point's location by
/// the given x- and y-offsets.
/// For example:
///
/// Point p = new Point(3,5);
/// p.Translate(-1,3);
///
/// results in p's having the value (2,8).
///
///

public void Translate(int xor, int yor) { X += xor; Y += yor;
}

3.
This tag allows example code within a comment, to specify how a method or other library member may be used. Ordinarily, this would also involve use of the tag (§A.2.2) as well.

Syntax:

description

Example:

See (§A.2.2) for an example.

4.
This tag provides a way to document the exceptions a method can throw.

Syntax:

description

where

cref="member"

The name of a member. The documentation generator checks that the given member exists and translates member to the canonical element name in the documentation file.

description

A description of the circumstances in which the exception is thrown.

Example:

public class DataBaseOperations
{
/// /// public static void ReadRecord(int flag) { if (flag == 1) throw new MasterFileFormatCorruptException(); else if (flag == 2) throw new MasterFileLockedOpenException(); // … }
}

5.
This tag allows including information from an XML document that is external to the source code file. The external file must be a well-formed XML document, and an XPath expression is applied to that document to specify what XML from that document to include. The tag is then replaced with the selected XML from the external document.

Syntax:

where

file="filename"

The file name of an external XML file. The file name is interpreted relative to the file that contains the include tag.

path="xpath"

An XPath expression that selects some of the XML in the external XML file.

Example:

If the source code contained a declaration like:

/// public class IntList { … }

and the external file “docs.xml” had the following contents:

Contains a list of integers.

Contains a list of integers.

then the same documentation is output as if the source code contained:

///
/// Contains a list of integers.
///
public class IntList { … }

6.
This tag is used to create a list or table of items. It may contain a block to define the heading row of either a table or definition list. (When defining a table, only an entry for term in the heading need be supplied.)

Each item in the list is specified with an block. When creating a definition list, both term and description must be specified. However, for a table, bulleted list, or numbered list, only description need be specified.

Syntax:

term description

term description … term description

where

term

The term to define, whose definition is in description.

description

Either an item in a bullet or numbered list, or the definition of a term.

Example:

public class MyClass
{
/// Here is an example of a bulleted list: /// /// /// Item 1. /// /// /// Item 2. /// /// /// public static void Main () { // ... }
}

7.
This tag is for use inside other tags, such as (§A.2.11) or (§A.2.12), and permits structure to be added to text.

Syntax:

content

where

content

The text of the paragraph.

Example:

/// This is the entry point of the Point class testing program.
/// This program tests each method and operator, and
/// is intended to be run after any non-trvial maintenance has
/// been performed on the Point class. public static void Main() { // ...
}

8.
This tag is used to describe a parameter for a method, constructor, or indexer.

Syntax:

description

where

name

The name of the parameter.

description

A description of the parameter.

Example:

/// This method changes the point's location to
/// the given coordinates.
/// the new x-coordinate.
/// the new y-coordinate. public void Move(int xor, int yor) { X = xor; Y = yor;
}

9.
This tag is used to indicate that a word is a parameter. The documentation file can be processed to format this parameter in some distinct way.

Syntax:

where

name

The name of the parameter.

Example:

/// This constructor initializes the new Point to
/// (,).
/// the new Point's x-coordinate.
/// the new Point's y-coordinate.

public Point(int xor, int yor) { X = xor; Y = yor;
}

10.
This tag allows the security accessibility of a member to be documented.

Syntax:

description

where

cref="member"

The name of a member. The documentation generator checks that the given code element exists and translates member to the canonical element name in the documentation file.

description

A description of the access to the member.

Example:

/// Everyone can
/// access this method.

public static void Test() { // ...
}

11.
This tag is used to specify extra information about a type. (Use (§A.2.15) to describe the type itself and the members of a type.)

Syntax:

description

where

description

The text of the remark.

Example:

/// Class Point models a point in a
/// two-dimensional plane.
/// Uses polar coordinates public class Point
{
// ...
}

12.
This tag is used to describe the return value of a method.

Syntax:

description

where

description

A description of the return value.

Example:

/// Report a point's location as a string.
/// A string representing a point's location, in the form (x,y),
/// without any leading, trailing, or embedded whitespace. public override string ToString() { return "(" + X + "," + Y + ")";
}

13.
This tag allows a link to be specified within text. Use (§A.2.14) to indicate text that is to appear in a See Also section.

Syntax:

where

cref="member"

The name of a member. The documentation generator checks that the given code element exists and changes member to the element name in the generated documentation file.

Example:

/// This method changes the point's location to
/// the given coordinates.
///
public void Move(int xor, int yor) { X = xor; Y = yor;
}

/// This method changes the point's location by
/// the given x- and y-offsets.
///
/// public void Translate(int xor, int yor) { X += xor; Y += yor;
}

14.
This tag allows an entry to be generated for the See Also section. Use (§A.2.13) to specify a link from within text.

Syntax:

where

cref="member"

The name of a member. The documentation generator checks that the given code element exists and changes member to the element name in the generated documentation file.

Example:

/// This method determines whether two Points have the same
/// location.
///
/// public override bool Equals(object o) { // ...
}

15.
This tag can be used to describe a type or a member of a type. Use (§A.2.11) to describe the type itself.

Syntax:

description

where

description

A summary of the type or member.

Example:

/// This constructor initializes the new Point to (0,0). public Point() : this(0,0) {
}

16.
This tag allows a property to be described.

Syntax:

property description

where

property description

A description for the property.

Example:

/// Property X represents the point's x-coordinate. public int X
{
get { return x; } set { x = value; }
}

17.
This tag is used to describe a generic type parameter for a class, struct, interface, delegate, or method.

Syntax:

description

where

name

The name of the type parameter.

description

A description of the type parameter.

Example:

/// A generic list class.
/// The type stored by the list. public class MyList { ...
}

18.
This tag is used to indicate that a word is a type parameter. The documentation file can be processed to format this type parameter in some distinct way.

Syntax:

where

name

The name of the type parameter.

Example:

/// This method fetches data and returns a list of ”/>”> .
/// query to execute

public List FetchData(string query) { ...
}

3. Processing the documentation file
The documentation generator generates an ID string for each element in the source code that is tagged with a documentation comment. This ID string uniquely identifies a source element. A documentation viewer can use an ID string to identify the corresponding metadata/reflection item to which the documentation applies.

The documentation file is not a hierarchical representation of the source code; rather, it is a flat list with a generated ID string for each element.

1. ID string format
The documentation generator observes the following rules when it generates the ID strings:

No white space is placed in the string.

The first part of the string identifies the kind of member being documented, via a single character followed by a colon. The following kinds of members are defined:

|Character |Description |
|E |Event |
|F |Field |
|M |Method (including constructors, destructors, and operators) |
|N |Namespace |
|P |Property (including indexers) |
|T |Type (such as class, delegate, enum, interface, and struct) |
|! |Error string; the rest of the string provides information about the error. For example, |
| |the documentation generator generates error information for links that cannot be |
| |resolved. |

The second part of the string is the fully qualified name of the element, starting at the root of the namespace. The name of the element, its enclosing type(s), and namespace are separated by periods. If the name of the item itself has periods, they are replaced by # (U+0023) characters. (It is assumed that no element has this character in its name.)

For methods and properties with arguments, the argument list follows, enclosed in parentheses. For those without arguments, the parentheses are omitted. The arguments are separated by commas. The encoding of each argument is the same as a CLI signature, as follows:

Arguments are represented by their documentation name, which is based on their fully qualified name, modified as follows:

Arguments that represent generic types have an appended “’” character followed by the number of type parameters

Arguments having the out or ref modifier have an @ following their type name. Arguments passed by value or via params have no special notation.

Arguments that are arrays are represented as [ lowerbound : size , … , lowerbound : size ] where the number of commas is the rank less one, and the lower bounds and size of each dimension, if known, are represented in decimal. If a lower bound or size is not specified, it is omitted. If the lower bound and size for a particular dimension are omitted, the “:” is omitted as well. Jagged arrays are represented by one “[]” per level.

Arguments that have pointer types other than void are represented using a * following the type name. A void pointer is represented using a type name of System.Void.

Arguments that refer to generic type parameters defined on types are encoded using the “`” character followed by the zero-based index of the type parameter.

Arguments that use generic type parameters defined in methods use a double-backtick “``” instead of the “`” used for types.

Arguments that refer to constructed generic types are encoded using the generic type, followed by “{“, followed by a comma-separated list of type arguments, followed by “}”.

2. ID string examples
The following examples each show a fragment of C# code, along with the ID string produced from each source element capable of having a documentation comment:

Types are represented using their fully qualified name, augmented with generic information:

enum Color { Red, Blue, Green }

namespace Acme
{
interface IProcess {...}

struct ValueType {...}

class Widget: IProcess { public class NestedClass {...}

public interface IMenuItem {...}

public delegate void Del(int i);

public enum Direction { North, South, East, West } }

class MyList { class Helper {...} }
}

"T:Color"
"T:Acme.IProcess"
"T:Acme.ValueType"
"T:Acme.Widget"
"T:Acme.Widget.NestedClass"
"T:Acme.Widget.IMenuItem"
"T:Acme.Widget.Del"
"T:Acme.Widget.Direction"
”T:Acme.MyList`1”
”T:Acme.MyList`1.Helper`2”

Fields are represented by their fully qualified name:

namespace Acme
{
struct ValueType { private int total; }

class Widget: IProcess { public class NestedClass { private int value; }

private string message; private static Color defaultColor; private const double PI = 3.14159; protected readonly double monthlyAverage; private long[] array1; private Widget[,] array2; private unsafe int *pCount; private unsafe float **ppValues; }
}

"F:Acme.ValueType.total"
"F:Acme.Widget.NestedClass.value"
"F:Acme.Widget.message"
"F:Acme.Widget.defaultColor"
"F:Acme.Widget.PI"
"F:Acme.Widget.monthlyAverage"
"F:Acme.Widget.array1"
"F:Acme.Widget.array2"
"F:Acme.Widget.pCount"
"F:Acme.Widget.ppValues"

Constructors.

namespace Acme
{
class Widget: IProcess { static Widget() {...}

public Widget() {...}

public Widget(string s) {...} }
}

"M:Acme.Widget.#cctor"
"M:Acme.Widget.#ctor"
"M:Acme.Widget.#ctor(System.String)"

Destructors.

namespace Acme
{
class Widget: IProcess { ~Widget() {...} }
}

"M:Acme.Widget.Finalize"

Methods.

namespace Acme
{
struct ValueType { public void M(int i) {...} }

class Widget: IProcess { public class NestedClass { public void M(int i) {...} }

public static void M0() {...} public void M1(char c, out float f, ref ValueType v) {...} public void M2(short[] x1, int[,] x2, long[][] x3) {...} public void M3(long[][] x3, Widget[][,,] x4) {...} public unsafe void M4(char *pc, Color **pf) {...} public unsafe void M5(void *pv, double *[][,] pd) {...} public void M6(int i, params object[] args) {...} }

class MyList { public void Test(T t) { } }

class UseList { public void Process(MyList list) { } public MyList GetValues(T inputValue) { return null; } }
}

"M:Acme.ValueType.M(System.Int32)"
"M:Acme.Widget.NestedClass.M(System.Int32)"
"M:Acme.Widget.M0"
"M:Acme.Widget.M1(System.Char,System.Single@,Acme.ValueType@)"
"M:Acme.Widget.M2(System.Int16[],System.Int32[0:,0:],System.Int64[][])"
"M:Acme.Widget.M3(System.Int64[][],Acme.Widget[0:,0:,0:][])"
"M:Acme.Widget.M4(System.Char*,Color**)"
"M:Acme.Widget.M5(System.Void*,System.Double*[0:,0:][])"
"M:Acme.Widget.M6(System.Int32,System.Object[])"
”M:Acme.MyList`1.Test(`0)”
”M:Acme.UseList.Process(Acme.MyList{System.Int32})”
”M:Acme.UseList.GetValues``(``0)”

Properties and indexers.

namespace Acme
{
class Widget: IProcess { public int Width { get {...} set {...} } public int this[int i] { get {...} set {...} } public int this[string s, int i] { get {...} set {...} } }
}

"P:Acme.Widget.Width"
"P:Acme.Widget.Item(System.Int32)"
"P:Acme.Widget.Item(System.String,System.Int32)"

Events.

namespace Acme
{
class Widget: IProcess { public event Del AnEvent; }
}

"E:Acme.Widget.AnEvent"

Unary operators.

namespace Acme
{
class Widget: IProcess { public static Widget operator+(Widget x) {...} }
}

"M:Acme.Widget.op_UnaryPlus(Acme.Widget)"

The complete set of unary operator function names used is as follows: op_UnaryPlus, op_UnaryNegation, op_LogicalNot, op_OnesComplement, op_Increment, op_Decrement, op_True, and op_False.

Binary operators.

namespace Acme
{
class Widget: IProcess { public static Widget operator+(Widget x1, Widget x2) {...} }
}

"M:Acme.Widget.op_Addition(Acme.Widget,Acme.Widget)"

The complete set of binary operator function names used is as follows: op_Addition, op_Subtraction, op_Multiply, op_Division, op_Modulus, op_BitwiseAnd, op_BitwiseOr, op_ExclusiveOr, op_LeftShift, op_RightShift, op_Equality, op_Inequality, op_LessThan, op_LessThanOrEqual, op_GreaterThan, and op_GreaterThanOrEqual.

Conversion operators have a trailing “~” followed by the return type.

namespace Acme
{
class Widget: IProcess { public static explicit operator int(Widget x) {...} public static implicit operator long(Widget x) {...} }
}

"M:Acme.Widget.op_Explicit(Acme.Widget)~System.Int32"
"M:Acme.Widget.op_Implicit(Acme.Widget)~System.Int64"

4. An example

1. C# source code
The following example shows the source code of a Point class:

namespace Graphics
{

/// Class Point models a point in a two-dimensional plane.
///
public class Point
{

/// Instance variable x represents the point's /// x-coordinate. private int x;

/// Instance variable y represents the point's /// y-coordinate. private int y;

/// Property X represents the point's x-coordinate. public int X { get { return x; } set { x = value; } }

/// Property Y represents the point's y-coordinate. public int Y { get { return y; } set { y = value; } }

/// This constructor initializes the new Point to /// (0,0). public Point() : this(0,0) {}

/// This constructor initializes the new Point to /// (,). /// xor is the new Point's x-coordinate. /// yor is the new Point's y-coordinate. public Point(int xor, int yor) { X = xor; Y = yor; }

/// This method changes the point's location to /// the given coordinates. /// xor is the new x-coordinate. /// yor is the new y-coordinate. /// public void Move(int xor, int yor) { X = xor; Y = yor; }

/// This method changes the point's location by /// the given x- and y-offsets. /// For example: /// /// Point p = new Point(3,5); /// p.Translate(-1,3); /// /// results in p's having the value (2,8). /// /// /// xor is the relative x-offset. /// yor is the relative y-offset. /// public void Translate(int xor, int yor) { X += xor; Y += yor; }

/// This method determines whether two Points have the same /// location. /// o is the object to be compared to the current object. /// /// True if the Points have the same location and they have /// the exact same type; otherwise, false. /// /// public override bool Equals(object o) { if (o == null) { return false; }

if (this == o) { return true; }

if (GetType() == o.GetType()) { Point p = (Point)o; return (X == p.X) && (Y == p.Y); } return false; }

/// Report a point's location as a string. /// A string representing a point's location, in the form (x,y), /// without any leading, training, or embedded whitespace. public override string ToString() { return "(" + X + "," + Y + ")"; }

/// This operator determines whether two Points have the same /// location. /// p1 is the first Point to be compared. /// p2 is the second Point to be compared. /// True if the Points have the same location and they have /// the exact same type; otherwise, false. /// /// public static bool operator==(Point p1, Point p2) { if ((object)p1 == null || (object)p2 == null) { return false; }

if (p1.GetType() == p2.GetType()) { return (p1.X == p2.X) && (p1.Y == p2.Y); }

return false; }

/// This operator determines whether two Points have the same /// location. /// p1 is the first Point to be compared. /// p2 is the second Point to be compared. /// True if the Points do not have the same location and the /// exact same type; otherwise, false. /// /// public static bool operator!=(Point p1, Point p2) { return !(p1 == p2); }

/// This is the entry point of the Point class testing /// program. /// This program tests each method and operator, and /// is intended to be run after any non-trvial maintenance has /// been performed on the Point class. public static void Main() { // class test code goes here }
}
}

2. Resulting XML
Here is the output produced by one documentation generator when given the source code for class Point, shown above:

Point

Class Point models a point in a two-dimensional plane.

Instance variable x represents the point's x-coordinate.

Instance variable y represents the point's y-coordinate.

This constructor initializes the new Point to (0,0).

This constructor initializes the new Point to (,). xor is the new Point's x-coordinate. yor is the new Point's y-coordinate.

This method changes the point's location to the given coordinates. xor is the new x-coordinate. yor is the new y-coordinate.

This method changes the point's location by the given x- and y-offsets. For example: Point p = new Point(3,5); p.Translate(-1,3); results in p's having the value (2,8).

xor is the relative x-offset. yor is the relative y-offset.

This method determines whether two Points have the same location. o is the object to be compared to the current object. True if the Points have the same location and they have the exact same type; otherwise, false.

Report a point's location as a string. A string representing a point's location, in the form (x,y), without any leading, training, or embedded whitespace.

This operator determines whether two Points have the same location. p1 is the first Point to be compared. p2 is the second Point to be compared. True if the Points have the same location and they have the exact same type; otherwise, false.

This operator determines whether two Points have the same location. p1 is the first Point to be compared. p2 is the second Point to be compared. True if the Points do not have the same location and the exact same type; otherwise, false.

This is the entry point of the Point class testing program. This program tests each method and operator, and is intended to be run after any non-trvial maintenance has been performed on the Point class.

Property X represents the point's x-coordinate.

Property Y represents the point's y-coordinate.

Grammar

This appendix contains summaries of the lexical and syntactic grammars found in the main document, and of the grammar extensions for unsafe code. Grammar productions appear here in the same order that they appear in the main document.

5. Lexical grammar input: input-sectionopt

input-section: input-section-part input-section input-section-part

input-section-part: input-elementsopt new-line pp-directive input-elements: input-element input-elements input-element

input-element: whitespace comment token 1. Line terminators new-line: Carriage return character (U+000D)
Line feed character (U+000A)
Carriage return character (U+000D) followed by line feed character (U+000A)
Next line character (U+0085)
Line separator character (U+2028)
Paragraph separator character (U+2029)

2. Comments comment: single-line-comment delimited-comment single-line-comment:
// input-charactersopt

input-characters: input-character input-characters input-character

input-character:
Any Unicode character except a new-line-character

new-line-character:
Carriage return character (U+000D)
Line feed character (U+000A)
Next line character (U+0085)
Line separator character (U+2028)
Paragraph separator character (U+2029)

delimited-comment:
/* delimited-comment-textopt asterisks /

delimited-comment-text: delimited-comment-section delimited-comment-text delimited-comment-section

delimited-comment-section:
/
asterisksopt not-slash-or-asterisk

asterisks:
*
asterisks *

not-slash-or-asterisk:
Any Unicode character except / or *

3. White space whitespace: Any character with Unicode class Zs
Horizontal tab character (U+0009)
Vertical tab character (U+000B)
Form feed character (U+000C)

4. Tokens token: identifier keyword integer-literal real-literal character-literal string-literal operator-or-punctuator

5. Unicode character escape sequences unicode-escape-sequence: \u hex-digit hex-digit hex-digit hex-digit
\U hex-digit hex-digit hex-digit hex-digit hex-digit hex-digit hex-digit hex-digit

6. Identifiers identifier: available-identifier
@ identifier-or-keyword

available-identifier:
An identifier-or-keyword that is not a keyword

identifier-or-keyword: identifier-start-character identifier-part-charactersopt

identifier-start-character: letter-character _ (the underscore character U+005F)

identifier-part-characters: identifier-part-character identifier-part-characters identifier-part-character

identifier-part-character: letter-character decimal-digit-character connecting-character combining-character formatting-character letter-character:
A Unicode character of classes Lu, Ll, Lt, Lm, Lo, or Nl
A unicode-escape-sequence representing a character of classes Lu, Ll, Lt, Lm, Lo, or Nl

combining-character:
A Unicode character of classes Mn or Mc
A unicode-escape-sequence representing a character of classes Mn or Mc

decimal-digit-character:
A Unicode character of the class Nd
A unicode-escape-sequence representing a character of the class Nd

connecting-character:
A Unicode character of the class Pc
A unicode-escape-sequence representing a character of the class Pc

formatting-character:
A Unicode character of the class Cf
A unicode-escape-sequence representing a character of the class Cf

7. Keywords keyword: one of abstract as base bool break byte case catch char checked class const continue decimal default delegate do double else enum event explicit extern false finally fixed float for foreach goto if implicit in int interface internal is lock long namespace new null object operator out override params private protected public readonly ref return sbyte sealed short sizeof stackalloc static string struct switch this throw true try typeof uint ulong unchecked unsafe ushort using virtual void volatile while

8. Literals literal: boolean-literal integer-literal real-literal character-literal string-literal null-literal boolean-literal: true false

integer-literal: decimal-integer-literal hexadecimal-integer-literal

decimal-integer-literal: decimal-digits integer-type-suffixopt

decimal-digits: decimal-digit decimal-digits decimal-digit

decimal-digit: one of
0 1 2 3 4 5 6 7 8 9

integer-type-suffix: one of
U u L l UL Ul uL ul LU Lu lU lu

hexadecimal-integer-literal:
0x hex-digits integer-type-suffixopt
0X hex-digits integer-type-suffixopt

hex-digits: hex-digit hex-digits hex-digit

hex-digit: one of
0 1 2 3 4 5 6 7 8 9 A B C D E F a b c d e f

real-literal: decimal-digits . decimal-digits exponent-partopt real-type-suffixopt
. decimal-digits exponent-partopt real-type-suffixopt decimal-digits exponent-part real-type-suffixopt decimal-digits real-type-suffix

exponent-part: e signopt decimal-digits
E signopt decimal-digits

sign: one of
+ -

real-type-suffix: one of
F f D d M m

character-literal:
' character '

character: single-character simple-escape-sequence hexadecimal-escape-sequence unicode-escape-sequence

single-character: Any character except ' (U+0027), \ (U+005C), and new-line-character

simple-escape-sequence: one of
\' \" \\ \0 \a \b \f \n \r \t \v

hexadecimal-escape-sequence:
\x hex-digit hex-digitopt hex-digitopt hex-digitopt

string-literal: regular-string-literal verbatim-string-literal

regular-string-literal:
" regular-string-literal-charactersopt "

regular-string-literal-characters: regular-string-literal-character regular-string-literal-characters regular-string-literal-character

regular-string-literal-character: single-regular-string-literal-character simple-escape-sequence hexadecimal-escape-sequence unicode-escape-sequence

single-regular-string-literal-character:
Any character except " (U+0022), \ (U+005C), and new-line-character

verbatim-string-literal:
@" verbatim-string-literal-charactersopt "

verbatim-string-literal-characters: verbatim-string-literal-character verbatim-string-literal-characters verbatim-string-literal-character

verbatim-string-literal-character: single-verbatim-string-literal-character quote-escape-sequence

single-verbatim-string-literal-character: any character except "

quote-escape-sequence:
""

null-literal: null 9. Operators and punctuators operator-or-punctuator: one of
{ } [ ] ( ) . , : ;
+ - * / % & | ^ ! ~
= < > ? ?? :: ++ -- && ||
-> == != = += -= *= /= %=
&= |= ^=

right-shift-assignment:
>|>=

10. Pre-processing directives pp-directive: pp-declaration pp-conditional pp-line pp-diagnostic pp-region pp-pragma conditional-symbol:
Any identifier-or-keyword except true or false

pp-expression: whitespaceopt pp-or-expression whitespaceopt

pp-or-expression: pp-and-expression pp-or-expression whitespaceopt || whitespaceopt pp-and-expression

pp-and-expression: pp-equality-expression pp-and-expression whitespaceopt && whitespaceopt pp-equality-expression

pp-equality-expression: pp-unary-expression pp-equality-expression whitespaceopt == whitespaceopt pp-unary-expression pp-equality-expression whitespaceopt != whitespaceopt pp-unary-expression

pp-unary-expression: pp-primary-expression ! whitespaceopt pp-unary-expression

pp-primary-expression: true false conditional-symbol ( whitespaceopt pp-expression whitespaceopt )

pp-declaration: whitespaceopt # whitespaceopt define whitespace conditional-symbol pp-new-line whitespaceopt # whitespaceopt undef whitespace conditional-symbol pp-new-line

pp-new-line: whitespaceopt single-line-commentopt new-line

pp-conditional: pp-if-section pp-elif-sectionsopt pp-else-sectionopt pp-endif

pp-if-section: whitespaceopt # whitespaceopt if whitespace pp-expression pp-new-line conditional-sectionopt

pp-elif-sections: pp-elif-section pp-elif-sections pp-elif-section

pp-elif-section: whitespaceopt # whitespaceopt elif whitespace pp-expression pp-new-line conditional-sectionopt

pp-else-section: whitespaceopt # whitespaceopt else pp-new-line conditional-sectionopt

pp-endif: whitespaceopt # whitespaceopt endif pp-new-line

conditional-section: input-section skipped-section

skipped-section: skipped-section-part skipped-section skipped-section-part

skipped-section-part: skipped-charactersopt new-line pp-directive skipped-characters: whitespaceopt not-number-sign input-charactersopt

not-number-sign:
Any input-character except #

pp-diagnostic: whitespaceopt # whitespaceopt error pp-message whitespaceopt # whitespaceopt warning pp-message

pp-message: new-line whitespace input-charactersopt new-line

pp-region: pp-start-region conditional-sectionopt pp-end-region

pp-start-region: whitespaceopt # whitespaceopt region pp-message

pp-end-region: whitespaceopt # whitespaceopt endregion pp-message

pp-line: whitespaceopt # whitespaceopt line whitespace line-indicator pp-new-line

line-indicator: decimal-digits whitespace file-name decimal-digits default hidden file-name:
" file-name-characters "

file-name-characters: file-name-character file-name-characters file-name-character

file-name-character:
Any input-character except "

pp-pragma: whitespaceopt # whitespaceopt pragma whitespace pragma-body pp-new-line

pragma-body: pragma-warning-body pragma-warning-body: warning whitespace warning-action warning whitespace warning-action whitespace warning-list

warning-action: disable restore

warning-list: decimal-digits warning-list whitespaceopt , whitespaceopt decimal-digits

6. Syntactic grammar

1. Basic concepts namespace-name: namespace-or-type-name

type-name: namespace-or-type-name namespace-or-type-name: identifier type-argument-listopt namespace-or-type-name . identifier type-argument-listopt qualified-alias-member 2. Types type: value-type reference-type type-parameter

value-type: struct-type enum-type

struct-type: type-name simple-type nullable-type simple-type: numeric-type bool

numeric-type: integral-type floating-point-type decimal integral-type: sbyte byte short ushort int uint long ulong char floating-point-type: float double

nullable-type: non-nullable-value-type ?

non-nullable-value-type: type enum-type: type-name reference-type: class-type interface-type array-type delegate-type

class-type: type-name object dynamic string

interface-type: type-name rank-specifiers: rank-specifier rank-specifiers rank-specifier

rank-specifier:
[ dim-separatorsopt ]

dim-separators:
,
dim-separators ,

delegate-type: type-name type-argument-list:
< type-arguments >

type-arguments: type-argument type-arguments , type-argument

type-argument: type type-parameter: identifier 3. Variables variable-reference: expression

4. Expressions argument-list: argument argument-list , argument

argument: argument-nameopt argument-value

argument-name: identifier :

argument-value: expression ref variable-reference out variable-reference

primary-expression: primary-no-array-creation-expression array-creation-expression

primary-no-array-creation-expression: literal simple-name parenthesized-expression member-access invocation-expression element-access this-access base-access post-increment-expression post-decrement-expression object-creation-expression delegate-creation-expression anonymous-object-creation-expression typeof-expression checked-expression unchecked-expression default-value-expression anonymous-method-expression simple-name: identifier type-argument-listopt

parenthesized-expression:
( expression )

member-access: primary-expression . identifier type-argument-listopt predefined-type . identifier type-argument-listopt qualified-alias-member . identifier

predefined-type: one of bool byte char decimal double float int long object sbyte short string uint ulong ushort

invocation-expression: primary-expression ( argument-listopt )

element-access: primary-no-array-creation-expression [ argument-list ]

this-access: this base-access: base . identifier base [ argument-list ]

post-increment-expression: primary-expression ++

post-decrement-expression: primary-expression --

object-creation-expression: new type ( argument-listopt ) object-or-collection-initializeropt new type object-or-collection-initializer

object-or-collection-initializer: object-initializer collection-initializer

object-initializer:
{ member-initializer-listopt }
{ member-initializer-list , }

member-initializer-list: member-initializer member-initializer-list , member-initializer

member-initializer: identifier = initializer-value

initializer-value: expression object-or-collection-initializer

collection-initializer:
{ element-initializer-list }
{ element-initializer-list , }

element-initializer-list: element-initializer element-initializer-list , element-initializer

element-initializer: non-assignment-expression { expression-list }

expression-list: expression expression-list , expression

array-creation-expression: new non-array-type [ expression-list ] rank-specifiersopt array-initializeropt new array-type array-initializer new rank-specifier array-initializer

delegate-creation-expression: new delegate-type ( expression )

anonymous-object-creation-expression: new anonymous-object-initializer

anonymous-object-initializer:
{ member-declarator-listopt }
{ member-declarator-list , }

member-declarator-list: member-declarator member-declarator-list , member-declarator

member-declarator: simple-name member-access identifier = expression

typeof-expression: typeof ( type ) typeof ( unbound-type-name ) typeof ( void )

unbound-type-name: identifier generic-dimension-specifieropt identifier :: identifier generic-dimension-specifieropt unbound-type-name . identifier generic-dimension-specifieropt

generic-dimension-specifier:
< commasopt >

commas:
,
commas ,

checked-expression: checked ( expression )

unchecked-expression: unchecked ( expression )

default-value-expression: default ( type )

unary-expression: primary-expression + unary-expression
- unary-expression
! unary-expression
~ unary-expression pre-increment-expression pre-decrement-expression cast-expression pre-increment-expression:
++ unary-expression

pre-decrement-expression:
-- unary-expression

cast-expression:
( type ) unary-expression

multiplicative-expression: unary-expression multiplicative-expression * unary-expression multiplicative-expression / unary-expression multiplicative-expression % unary-expression

additive-expression: multiplicative-expression additive-expression + multiplicative-expression additive-expression – multiplicative-expression

shift-expression: additive-expression shift-expression shift-expression relational-expression = shift-expression relational-expression is type relational-expression as type

equality-expression: relational-expression equality-expression == relational-expression equality-expression != relational-expression

and-expression: equality-expression and-expression & equality-expression

exclusive-or-expression: and-expression exclusive-or-expression ^ and-expression

inclusive-or-expression: exclusive-or-expression inclusive-or-expression | exclusive-or-expression

conditional-and-expression: inclusive-or-expression conditional-and-expression && inclusive-or-expression

conditional-or-expression: conditional-and-expression conditional-or-expression || conditional-and-expression

null-coalescing-expression: conditional-or-expression conditional-or-expression ?? null-coalescing-expression

conditional-expression: null-coalescing-expression null-coalescing-expression ? expression : expression

lambda-expression: anonymous-function-signature => anonymous-function-body

anonymous-method-expression: delegate explicit-anonymous-function-signatureopt block

anonymous-function-signature: explicit-anonymous-function-signature implicit-anonymous-function-signature

explicit-anonymous-function-signature:
( explicit-anonymous-function-parameter-listopt )

explicit-anonymous-function-parameter-list: explicit-anonymous-function-parameter explicit-anonymous-function-parameter-list , explicit-anonymous-function-parameter

explicit-anonymous-function-parameter: anonymous-function-parameter-modifieropt type identifier

anonymous-function-parameter-modifier: ref out

implicit-anonymous-function-signature:
( implicit-anonymous-function-parameter-listopt ) implicit-anonymous-function-parameter implicit-anonymous-function-parameter-list: implicit-anonymous-function-parameter implicit-anonymous-function-parameter-list , implicit-anonymous-function-parameter

implicit-anonymous-function-parameter: identifier anonymous-function-body: expression block

query-expression: from-clause query-body

from-clause: from typeopt identifier in expression

query-body: query-body-clausesopt select-or-group-clause query-continuationopt

query-body-clauses: query-body-clause query-body-clauses query-body-clause

query-body-clause: from-clause let-clause where-clause join-clause join-into-clause orderby-clause

let-clause: let identifier = expression

where-clause: where boolean-expression

join-clause: join typeopt identifier in expression on expression equals expression

join-into-clause: join typeopt identifier in expression on expression equals expression into identifier

orderby-clause: orderby orderings

orderings: ordering orderings , ordering

ordering: expression ordering-directionopt

ordering-direction: ascending descending

select-or-group-clause: select-clause group-clause

select-clause: select expression

group-clause: group expression by expression

query-continuation: into identifier query-body

assignment: unary-expression assignment-operator expression

assignment-operator:
=
+=
-=
*=
/=
%=
&=
|=
^=
=

variant-type-parameters: attributesopt variance-annotationopt type-parameter variant-type-parameters , attributesopt variance-annotationopt type-parameter

variance-annotation: in out

interface-base:
: interface-type-list

interface-body:
{ interface-member-declarationsopt }

interface-member-declarations: interface-member-declaration interface-member-declarations interface-member-declaration

interface-member-declaration: interface-method-declaration interface-property-declaration interface-event-declaration interface-indexer-declaration

interface-method-declaration: attributesopt newopt return-type identifier type-parameter-list ( formal-parameter-listopt ) type-parameter-constraints-clausesopt ;

interface-property-declaration: attributesopt newopt type identifier { interface-accessors }

interface-accessors: attributesopt get ; attributesopt set ; attributesopt get ; attributesopt set ; attributesopt set ; attributesopt get ;

interface-event-declaration: attributesopt newopt event type identifier ;

interface-indexer-declaration: attributesopt newopt type this [ formal-parameter-list ] { interface-accessors }

11. Enums enum-declaration: attributesopt enum-modifiersopt enum identifier enum-baseopt enum-body ;opt

enum-base:
: integral-type

enum-body:
{ enum-member-declarationsopt }
{ enum-member-declarations , }

enum-modifiers: enum-modifier enum-modifiers enum-modifier

enum-modifier: new public protected internal private enum-member-declarations: enum-member-declaration enum-member-declarations , enum-member-declaration

enum-member-declaration: attributesopt identifier attributesopt identifier = constant-expression

12. Delegates delegate-declaration: attributesopt delegate-modifiersopt delegate return-type identifier variant-type-parameter-listopt ( formal-parameter-listopt ) type-parameter-constraints-clausesopt ;

delegate-modifiers: delegate-modifier delegate-modifiers delegate-modifier

delegate-modifier: new public protected internal private 13. Attributes global-attributes: global-attribute-sections

global-attribute-sections: global-attribute-section global-attribute-sections global-attribute-section

global-attribute-section:
[ global-attribute-target-specifier attribute-list ]
[ global-attribute-target-specifier attribute-list , ]

global-attribute-target-specifier: global-attribute-target :

global-attribute-target: assembly module

attributes: attribute-sections attribute-sections: attribute-section attribute-sections attribute-section

attribute-section:
[ attribute-target-specifieropt attribute-list ]
[ attribute-target-specifieropt attribute-list , ]

attribute-target-specifier: attribute-target :

attribute-target: field event method param property return type attribute-list: attribute attribute-list , attribute

attribute: attribute-name attribute-argumentsopt

attribute-name: type-name

attribute-arguments:
( positional-argument-listopt )
( positional-argument-list , named-argument-list )
( named-argument-list )

positional-argument-list: positional-argument positional-argument-list , positional-argument

positional-argument: argument-nameopt attribute-argument-expression

named-argument-list: named-argument named-argument-list , named-argument

named-argument: identifier = attribute-argument-expression

attribute-argument-expression: expression 7. Grammar extensions for unsafe code class-modifier: ... unsafe struct-modifier:
...
unsafe

interface-modifier:
...
unsafe

delegate-modifier:
...
unsafe

field-modifier:
...
unsafe

method-modifier:
...
unsafe

property-modifier:
...
unsafe

event-modifier:
...
unsafe

indexer-modifier:
...
unsafe

operator-modifier:
...
unsafe

constructor-modifier:
...
unsafe

destructor-declaration: attributesopt externopt unsafeopt ~ identifier ( ) destructor-body attributesopt unsafeopt externopt ~ identifier ( ) destructor-body

static-constructor-modifiers: externopt unsafeopt static unsafeopt externopt static externopt static unsafeopt unsafeopt static externopt static externopt unsafeopt static unsafeopt externopt

embedded-statement:
...
unsafe-statement fixed-statement unsafe-statement: unsafe block

type:
...
pointer-type

pointer-type: unmanaged-type * void *

unmanaged-type: type primary-no-array-creation-expression:
...
pointer-member-access pointer-element-access sizeof-expression

unary-expression:
...
pointer-indirection-expression addressof-expression pointer-indirection-expression:
* unary-expression

pointer-member-access: primary-expression -> identifier

pointer-element-access: primary-no-array-creation-expression [ expression ]

addressof-expression:
& unary-expression

sizeof-expression: sizeof ( unmanaged-type )

fixed-statement: fixed ( pointer-type fixed-pointer-declarators ) embedded-statement

fixed-pointer-declarators: fixed-pointer-declarator fixed-pointer-declarators , fixed-pointer-declarator

fixed-pointer-declarator: identifier = fixed-pointer-initializer

fixed-pointer-initializer:
& variable-reference expression struct-member-declaration:
…
fixed-size-buffer-declaration

fixed-size-buffer-declaration: attributesopt fixed-size-buffer-modifiersopt fixed buffer-element-type fixed-size-buffer-declarators ;

fixed-size-buffer-modifiers: fixed-size-buffer-modifier fixed-size-buffer-modifier fixed-size-buffer-modifiers

fixed-size-buffer-modifier: new public protected internal private unsafe

buffer-element-type: type fixed-size-buffer-declarators: fixed-size-buffer-declarator fixed-size-buffer-declarator fixed-size-buffer-declarators

fixed-size-buffer-declarator: identifier [ constant-expression ]

local-variable-initializer:
…
stackalloc-initializer

stackalloc-initializer: stackalloc unmanaged-type [ expression ]

References

Unicode Consortium. The Unicode Standard, Version 3.0. Addison-Wesley, Reading, Massachusetts, 2000, ISBN 0-201-616335-5.

IEEE. IEEE Standard for Binary Floating-Point Arithmetic. ANSI/IEEE Standard 754-1985. Available from http://www.ieee.org.

ISO/IEC. C++. ANSI/ISO/IEC 14882:1998.