Shorten VAR Byte Statements?

Humanoido

VAR
...
byte state30
byte state31
byte state32
byte state33
byte state34
byte state35
byte state36
byte state37
byte state38
byte state39
...

The program has a lot of these statements.
Is there any way to shorten it, to one statement?
Thanks in advance.

Humanoido

Heater.

What about using an array:

byte state[10]

Phil Pilgrim (PhiPi)

Or, if you don't want an array, this also works:

VAR
  ...
  byte state30, state31, state32, state33, state34
  byte state35, state36, state37, state38, state39
  ...

But, based on how you've named your variables, I suspect an array would be a better solution.

-Phil

Humanoido

Phil Pilgrim (PhiPi) wrote: »

Or, if you don't want an array, this also works:

VAR
  ...
  byte state30, state31, state32, state33, state34
  byte state35, state36, state37, state38, state39
  ...

But, based on how you've named your variables, I suspect an array would be a better solution.

-Phil

Phil, will that code use considerably less memory over an array?

Phil Pilgrim (PhiPi)

The amount memory used for the VARs will be the same, whether they're individual variables or a large array. But, by using an array and code with indexing, rather than treating each byte as a special case, you could save code space.

-Phil

localroger

I am wondering if you actually need separate bytes for these or if they might not be consts defining different states of your system? You don't actually need to reserve storage for consts, they just become names for the states which you can compare in event code.

con

#0 {start at zero}
st_idle {cons with no val increment by 1}
st_wakeup
st_lookaround
st_verify_id
st_approach
st_bite

I can't really imagine what you would be doing with separate state vars enumerated like that. The whole point of a state machine is to have as few state vars as possible so you can avoid pathological or unanticipated combination states.