Question

Possible Duplicate:
Child Scope & CS0136
C# Variable Scoping

Though I have been using C# for quite some time, I have just stumbled upon this error.

If I have the following:

if(true)
{
    int x = 0;
}
int x = 0;

I get an error that says: A local variable named 'x' cannot be declared in this scope because it would give a different meaning to 'x', which is already used in a child scope to denote something else.

And if I do this:

if(true)
{
    int x = 0;
} 
x = 0;

I get an error that says: The name 'x' does not exist in the current context.

I can understand having one or the other, but why do both of these errors exist? Is there a way around the first option? I find it very annoying.

Thanks.

Answer 1

Both of these errors exist to stop you from making mistakes or causing your colleagues to want to kill you.

The first fails because it’s confusing to have two identically named local variables both in scope at a time.

The second fails because the variable’s scope is the if statement, and you’re trying to access it outside that scope.

If you want a single variable which you can use both inside and outside the block, you just need to declare it before the block:

int x;
if (true)
{
    x = 0;
}
x = 0;

If you actually want two separate variables to be in scope at the same time (within the block), then give them different names – thereby avoiding later confusion.

EDIT: You can declare multiple local variables with the same name in a single method, but they have to have separate scopes. For example:

public void Foo(IEnumerable<string> values)
{
    double sum = 0;
    foreach (string x in values)
    {
        int z = x.Length;
        sum += z;
    }

    foreach (string x in values)
    {
        double z = double.Parse(x);
        sum += z;
    }
}

Personally I don’t tend to use this ability very often – at least not with different types – when the variables have meaningful names and methods are short. But it’s absolutely legitimate, and can certainly be useful sometimes.