Use key to get itself

[ben_lubar]

Is if not a flow-control statement?

[riking]

I think that Go really gets this one right. Any new variables you introduce after the flow-control keyword are scoped to the block that follows. if (both branches), for, and switch.

The Go Programming Language Specification - The Go Programming Language

The TypeSwitchGuard may include a short variable declaration. When that form is used, the variable is declared at the beginning of the implicit block in each clause. In clauses with a case listing exactly one type, the variable has that type; otherwise, the variable has the type of the expression in the TypeSwitchGuard.

[RaceProUK]

It is; I've never seen anyone define a variable in an if statement though.

[ben_lubar]

http://what.thedailywtf.com/t/use-key-to-get-itself/8481/9?u=ben_lubar

[RaceProUK]

C#6 hasn't been officially released yet (only preview), so it doesn't count

[tar]

@RaceProUK said:

a variable in an if statement

Works nicely with pointers in C++:

System &sys = /*...*/;

if(SubSystem *subsys = sys.get_optional_subsystem()) {
    // do stuff with 'subsys'...
}
// 'subsys' is out of scope now...

[RaceProUK]

@tar said:

Works nicely with pointers in C++:

C# requires the result of the expression to be bool. And it won't coerce.

[tar]

@RaceProUK said:

C# requires the result of the expression to be bool. And it won't coerce.

:fail.pfx:

[eskel]

@RaceProUK said:

The braces are implied for flow-control statements, and for scoping purposes, the flow-control statement itself is scoped to the (implied) braces.

Up to the point of reading that I'd been ignorant-but-curious towards C#.

[blakeyrat]

And now you are...? Hot and bothered towards C#? Itching and burning for C#?

[eskel]

@blakeyrat said:

Itching and burning for C#

That one. Yeah, definitely that one.
googles
Wait. No it isn't.

[tar]

Ask your doctor if a C# prescription is right for you.

[another_sam]

@dcon said:

Wait, so "for (int i = 0; i < 3; ++i) dosomething(i);" (I'm assuming that's valid C#, as well as C++) means i survives after the 'for'? If so, that's just wrong. If no, then the previous example is just wrong.

What's wrong is the lack of braces.

[ben_lubar]

Also, why are there parentheses around two statements and an expression? That's not what parentheses are normally around!

[tar]

@dcon said:

(I'm assuming that's valid C#, as well as C++)

@ben_lubar said:

Also, why are there parentheses around two statements and an expression?

Because it indicates that these are subordinate to the main thrust of the argument.