Welcome to the Lounge

if (oldState == "state1" && newState == "state2")
{
}
else if (oldState == "state2" && newState == "state3")
{
}
else if .. else if .. else if .. else { }
// line 1000

public class StateClass
{
public static string oldState;
public static string newState;
}

public class DifferentClass
{
//...
StateClass.oldState = "whatever";
StateClass.newState = "something";
//...
SomeControl.Text = StateClass.newState;
}

public class AnotherClass
{
private object field1;
//...
private object field90;
//...
if (StateClass.oldState == null) throw new Exception("State not set.");
if (StateClass.oldState == "state1" && StateClass.newState == "state2")
{
SomePublicOrStaticVar = "";
}
else if (StateClass.oldState == "state2" && StateClass.newState == "state3")
{
}
else if .. else if .. else if .. else { }
// line 1000
//...
}

honey the codewitch wrote:

They should be used as sparsely as possible and no sparser.

If comments get stale, that's not the fault of comments but the developer.

Jeremy Falcon wrote:

If comments get stale, that's not the fault of comments but the developer.

M.D.V.

If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.

Nelek wrote:

The same with code.

Nelek wrote:

In the PLC world it is a wide extended practice to just add a "AND 0" at the beginning of a code segment to anulate it. That's even worst than commenting it out, because it appears in the cross references as well, commented code doesn't.

Nelek wrote:

I once refactored a program of the "Senior" that taught me whe I started, because it was a PITA to work with it.