2

msdn documentation on out says that a parameter passed as out must be assigned a value inside the function. Example from the website:

class OutExample
{
    static void Method(out int i)
    {
        i = 44;
    }
    static void Main()
    {
        int value;
        Method(out value);
       // value is now 44
    }
 }

According to my understanding when the int "value" is declared it is already assigned a default value of 0 (since int is a value type and cannot be null.) So why would it be necessary that "Method" modify its value?

Similarly, if "ref" were to be used instead of out, would there be any need of initializing "value"?

There are questions like this What's the difference between the 'ref' and 'out' keywords? but no one wants to put 2 and 2 together.

Community
  • 1
  • 1
meonstackexchange
  • 609
  • 5
  • 9

4 Answers4

5

According to my understanding when the int "value" is declared it is already assigned a default value of 0 (since int is a value type and cannot be null.)

No, that's not correct.

A local variable isn't assigned a value when it is created. The space for local variables are created by moving the stack pointer to make room for them on the stack. That memory area is not cleared, it will contain any values that happened to be there.

The compiler forces you to assign a value to the variable before it can be used, so that the "garbage" value that it originally contains never will be used.

Similarly, if "ref" were to be used instead of out, would there be any need of initializing "value"?

The value wouldn't need to be set in the method, as it already has a value. The variable used to call the method would need to be initialised though:

static void Method(ref int i) {
    // doesn't need to set the value
}

static void Main() {
    int value;
    value = 42; // needs to be initialised before the call
    Method(ref value);
   // value is still 42
}
Guffa
  • 687,336
  • 108
  • 737
  • 1,005
  • I don't think there is any "garbage" value. `int` would be assigned a default value of `0` and when a variable is only declared it is unassigned. There is no concept of garbage value in.Net like C,C++. – CriketerOnSO Apr 14 '15 at 19:44
  • `out` only specifies that the method **will** modify the value of the parameter. Even if that parameter is assigned some "non-garbage" value. – CriketerOnSO Apr 14 '15 at 19:45
  • For local variables of simple value types like ``int``, the compiler prevents use of the variable before it is assigned a value. Object member variables and arrays on the other hand are initialized to their default values when the object is created (i.e. the memory is cleared and set to all 0's). – Christopher Hamkins Jan 05 '23 at 08:45
1

An int is not assigned a value by default, even though there is a default value...try this:

Console.WriteLine(default(int)); // output = '0'
int foo;
Console.WriteLine(foo); // compile error - Use of unassigned local variable

The contract for out parameters is that the method is guaranteed to assign a value to it. The contract for ref parameters has no such guarantee.

Rufus L
  • 36,127
  • 5
  • 30
  • 43
0

You have to assign value to the variable. But the notion of out parameter, you've mentioned in post, has more semantical meaning.

If you pass out parameter you expect that the function you call has to assign it. C# compiler simply enforced that "good programmer" skill to compilation time control, for better code style.

Tigran
  • 61,654
  • 8
  • 86
  • 123
0

Sometimes from your methods you need to return more than one value, so in that case you can return those extra values through ref and out parameteres. A good reference to these are the "TryParse" methods from .NET framework, for instance the "Int32.TryParse Method"

[1]: https://msdn.microsoft.com/en-us/library/f02979c7%28v=vs.110%29.aspx

You can find more on the above link in the MSDN.

Clock
  • 974
  • 3
  • 17
  • 35