For every value type or pointer type V, there is a corresponding pointer type V*. A pointer instance holds the address of a value. This is considered to be of type V, but pointer types can be (unsafely) cast to any other pointer type.

The main pointer operators are listed below.

By marking a type, type member, or statement block with the unsafe keyword, you’re permitted to use pointer types and perform C++ style pointer operations on memory within that scope. Here is an example of using pointers to quickly process a bitmap:

	unsafe void RedFilter(int[,] bitmap)
	{
	  int length = bitmap.Length;
	  fixed (int* b = bitmap)
	  {
	    int* p = b;
	    for(int i = 0; i < length; i++)
	      *p++ &= 0xFF;
	  }
	}

Unsafe code can run faster than a corresponding safe implementation. In this case, the code would have required a nested loop with array indexing and bounds checking. An unsafe C# method may also be faster than calling an external C function because there is no overhead associated with leaving the managed execution environment.

The fixed statement is required to pin a managed object, such as the bitmap in the previous example. During the execution of a program, many objects are allocated and deallocated from the heap. To avoid unnecessary waste or fragmentation of memory, the garbage collector moves objects around. Pointing to an object is futile if its address could change while referencing it, so the fixed statement tells the garbage collector to “pin” the object and not move it around. This may have an impact on the efficiency of the runtime, so fixed blocks should be used only briefly, and heap allocation should be avoided within the fixed block.

Within a fixed statement, you can get a pointer to any value type, an array of value types, or a string. In the case of arrays and strings, the pointer will actually point to the first element, which is a value type.

Value types declared inline within reference types require the reference type to be pinned, as follows:

	class Test
	{
	  int x;
	  static void Main()
	  {
	    Test test = new Test();
	    unsafe
	    {
	       fixed (int* p = &test.x) // pins test
	       {
	         *p = 9;
	       }
	       System.Console.WriteLine (test.x);
	    }
	  }
	}

In addition to the & and * operators, C# also provides the C++ style -> operator, which can be used on structs:

	struct Test
	{
	  int x;
	  unsafe static void Main()
	  {
	    Test test = new Test();
	    Test* p = &test;
	    p->x = 9;
	    System.Console.WriteLine (test.x);
	  }
	}

Rather than pointing to a specific value type, a pointer may make no assumptions about the type of the underlying data. This approach is useful for functions that deal with raw memory. An implicit conversion exists from any pointer type to void*. A void* cannot be dereferenced and arithmetic operations cannot be performed on void pointers. For example:

	class Test
	{
	  unsafe static void Main()
	  {
	    short[ ] a = {1,1,2,3,5,8,13,21,34,55};
	      fixed (short* p = a)
	      {
	        //sizeof returns size of value-type in bytes
	        Zap (p, a.Length * sizeof (short));
	      }
	    foreach (short x in a)
	      System.Console.WriteLine (x); // prints all zeros
	  }
	  unsafe static void Zap (void* memory, int byteCount)
	  {
	    byte* b = (byte*)memory;
	      for (int i = 0; i < byteCount; i++)
	        *b++ = 0;
	  }
	}

Pointers are also useful for accessing data outside the managed heap (such as when interacting with C DLLs or COM), or when dealing with data not in the main memory (such as graphics memory or a storage medium on an embedded device).