Modes and States

[danvim]

Proposed syntaxes

__Mode<<COMP

__     settings identifier
Mode   setting name
<<     setting assignment token
COMP   parameter value

Resulting Actions and Consequences

The parser will acknowledge the change of mode and the state shall be store in a new Object called States. Functions shall acknowledge the changed state and run and throw errors according to rules of calculation within that state.

Related Functionalities

• Base change: e.g. __Base<<2
• Console output settings __PrintSteps<<1

[bryanchun]

So it is now

__Mode<<PossibleMode

does this mean generally

__State<<PossibleState

by also considering Base and PrintSteps?

[danvim]

@bryanchun Basically, yes. There should be a way to easily identify a setting (with least amount of hard code) and using operators unused by other operations.

The __ and << are just one of the possibilities. The reason I didn't suggest using = to set the state is because = means differently in mathematics, though we can still opt for =