Stack Exchange network consists of 183 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.
Visit Stack Exchange
Stack Internal
Knowledge at work
Bring the best of human thought and AI automation together at your work.
Explore Stack InternalI agree that reusing variable is more often than not a code smell. Probably such code should be refactored in smaller, self-contained, blocks.
There is one particular scenario, OTOH, in C#, when they tend to popup - that is when using switch-case constructs. Situation is very nicely explained in: C# Switch statement with/without curly brackets… what's the difference?C# Switch statement with/without curly brackets… what's the difference?
I agree that reusing variable is more often than not a code smell. Probably such code should be refactored in smaller, self-contained, blocks.
There is one particular scenario, OTOH, in C#, when they tend to popup - that is when using switch-case constructs. Situation is very nicely explained in: C# Switch statement with/without curly brackets… what's the difference?
I agree that reusing variable is more often than not a code smell. Probably such code should be refactored in smaller, self-contained, blocks.
There is one particular scenario, OTOH, in C#, when they tend to popup - that is when using switch-case constructs. Situation is very nicely explained in: C# Switch statement with/without curly brackets… what's the difference?
I agree that reusing variable is more often than not a code smell. Probably such code should be refactored in smaller, self-contained, blocks.
There is one particular scenario, OTOH, in C#, when they tend to popup - that is when using switch-case constructs. Situation is very nicely explained in:
I agree that reusing variable is more often than not a code smell. Probably such code should be refactored in smaller, self-contained, blocks.
There is one particular scenario, OTOH, in C#, when they tend to popup - that is when using switch-case constructs. Situation is very nicely explained in:
I agree that reusing variable is more often than not a code smell. Probably such code should be refactored in smaller, self-contained, blocks.
There is one particular scenario, OTOH, in C#, when they tend to popup - that is when using switch-case constructs. Situation is very nicely explained in: C# Switch statement with/without curly brackets… what's the difference?
I agree that reusing variable is more often than not a code smell. Probably such code should be refactored in smaller, self-contained, blocks.
There is one particular scenario, OTOH, in C#, when they tend to popup - that is when using switch-case constructs. Situation is very nicely explained in:
