CSharp fixed keyword
Since I’ve already mentioned my bias against using unsafe mode in this post:
I’ll skip my normal rant about that. Just suffice it to say they don’t call it “unsafe” for nothing.
So assuming you have some valid use for using unsafe mode, you’ll also need to make sure your memory isn’t moving around on you while you are accessing the pointers you’ve created in your unsafe block. For that, you’ll need the fixed keyword.
While the unsafe mode gives you the ability to use pointers in the first place, fixed makes sure the pointers aren’t moving around while you are using them. We need both so that we only fix the memory in its location while we are using it while still being able to write normal code within our unsafe block.
To create a pointer to a variable, you use the asterisk (*). To retrieve the address of a variable (so you can assign it to the variable) you use the ampersand (&). Just like we did in C++ for those of you who are familiar with that language.
So to create a pointer to an integer, your code might look something like this:
public unsafe void Foo() { int i = 20; int* pi = &i; }
At this point, pi points to i, which holds the value of 20.
But if we want to use pi to retrieve the value of 20, we want to make sure that the memory location of i doesn’t move while we are retrieving it.
Arguably, this is much more important when we are trying to access arrays in a loop. But to keep the illustration simple we’ll continue with retrieving our single integer value.
public unsafe void Foo() { int i = 20; int copyOfI; fixed (int* pi = &i) { copyOfI = *pi; } }
Now we can be sure that every time we access pi, it will still be pointing to the variable i.
Other post in Advanced CSharp
- Two Interfaces. Same Method. Two meanings. - September 29th, 2008
- Making values nullable - October 9th, 2008
- CSharp's Property Shortcuts - October 23rd, 2008
- Readonly variables in CSharp? Really?! - October 29th, 2008
- Dispose with Using - November 10th, 2008
- Delegates in .NET - December 4th, 2008
- Using Sealed in CSharp - December 8th, 2008
- CSharp checked and unchecked - December 11th, 2008
- Advanced CSharp - unsafe mode - December 15th, 2008
- Volatile variables and CSharp threads - December 22nd, 2008
- What is the global keyword in CSharp? - December 29th, 2008
- CSharp fixed keyword - January 5th, 2009
- using - There's more there than you are using - February 2nd, 2009
- Stackalloc in CSharp - February 16th, 2009
- Removing Warnings from CSharp Compile Cycle - March 10th, 2009
- && vs & and | vs ||... What's the difference? - March 16th, 2009
- Advanced CSharp - yield - March 25th, 2009
- Just say “No!” to C# Regions? Really?! - April 16th, 2009
- C# “” better than string.Empty? - April 20th, 2009
- .Net String Pool – Not Just For The Compiler - April 22nd, 2009
- CSharp ?? Operator - May 18th, 2009
- Using VB.NET From CSharp - July 1st, 2009
- Dispose, Finalize and SuppressFinalize - July 9th, 2009
- What is .NET’s Object.GetHashCode() Used For? - August 5th, 2009
- ASP.NET Substitution Control - October 22nd, 2009
Other Related Items:
Audiovox XMSC1 Sureconnect Adapter for Xpress-R Xm Satellite RadioProvides a clear signal from XM plug-and-play FM transmitters * connects directly to your vehicle's fixed or in-glass antenna
Milwaukee 5615-24 1.75-Horsepower Multi-Base Router Kit Includes Plunge Base and BodyGrip Fixed BaseMulti-Base Router Kits Type: Router Kit (Fixed & Plunge) Type of Power: Electric Collet Size: 1/4 - 1/2 Minimum RPM: 24000 Maximum RPM: 24000 Amperage Rating: 11.0 Horsepower: 1-3/4
If you're new here, you may want to subscribe to my RSS feed. Thanks for visiting!










[...] CSharp fixed Keyword (Dave M. Bush) [...]
In which case would you not want to used the fixed keyword? Maybe I am a little slow today, but I can’t think of a scenario where you would want to point to something that is moving around in memory space?
I’ve been thinking about this question since you posted it and I’ve come to the conclusion that you either don’t understand the context in which this was written or I don’t understand your question.
cPanel VPS. I understand your confusion and let me add this explanation. You use fixed so garbage collection won’t clean up your variable. You always want to use fixed. It says while i am in this fixed code block please don’t clean up the information I am pointing to.
If my statement is still not clear, here is the msdn article
http://msdn.microsoft.com/en-us/library/f58wzh21.aspx
To be clear on the “always want to use fixed.” You always want to use it when you are working with memory in unsafe mode. Normal, day-to-day usage of .NET, you’d never want to use it.