
This is the Title of the Book, eMatter Edition
Copyright © 2007 O’Reilly & Associates, Inc. All rights reserved.
Comparing Pointers
|
1069
This mistake is easy to make, especially as the code gets more and more complex.
This error can also occur when returning a pointer from a method as a return value.
To solve this, you need to not assign local variables that are created on the stack in
the scope of the method to the pointer, since the value being pointed to can “go
away” once the scope is exited, creating a dangling pointer.
Be very careful that you do not create dangling pointers (a pointer that
doesn’t point at anything valid, such as by assigning a pointer to mem-
ory that is collected before leaving the function) when passing pointer
parameters as
ref or out. This warning also applies to pointers used as
return values.
See Also
See the “Method Parameters,” “out Parameter,” and “ref Parameter” topics in the
MSDN documentation.
19.2 Comparing Pointers
Problem
You need to know whether two pointers point to the same memory location. If they
don’t, you need to know which of the two pointers points to a higher or lower ele-
ment in the same block of memory.
Solution
Using the == and != operators, you can determine if two pointers point to the same
memory location. For example, the code:
unsafe
{
int[] arr = new int[5] {1,2,3,4,5};
fixed(int* ptrArr = &arr[0])
{
int* p1 = (ptrArr + 1);
int* p2 = (ptrArr + ...