C#

unsafe static void WriteLocations() 
 {
  int *p;
  int i;
  i = 10;
  p = &i;


  string addr;
  addr = int.Format((int) p, "X");
  //To Format the Pointer to a String

  Console.WriteLine(addr);
  Console.WriteLine(*p);

  *p = 333;
  Console.WriteLine(i);
  //Change the Value using Pointer

  i = *(&i) + 10;
  Console.WriteLine(i);

 }

void DoSomething() // safe function
{
    unsafe // unsafe block of code in safe function
    {
        // use pointers here
    }
}

• code that cannot be verified as type-safe by the .NET Common Language Runtime (CLR).
• is not Common Language Specification (CLS)-compliant, meaning that other .NET languages like VB.NET, J#, and so on are not required to implement nor are they guaranteed to consume such code, if it were declared as public and made available to other .NET dlls & executables.
• requires a full trust security scenario in order to run, for instance, it must be installed/run from the target machine; if you try to use pointers in code run in a partial-trust scenario (e.g. a C# applet over the internet), the .NET CLR will throw a SecurityException because pointers require full access to the machine's memory, thus are potentially dangerous to the end user.
For a function, class, or code block to be unsafe, just use the unsafe keyword:



unsafe class MyClass
{
}

unsafe void MyFunction()
{
}

void MyFunctionWithUnsafeBlock
{

unsafe
{
}

}



Despite all these cautions, you're free to use pointers as much as you like if your application is a standalone app or dll, indeed, the .NET framework uses pointers internally quite often for performance gains and interop scenarios.



Tech, life, family, faith: Give me a visit.
I'm currently blogging about: Homosexuality in Christianity
Judah Himango