Hi Jim, No flame taken.. you made the jump 30 years ago!
Maybe I need to look at this a bit differently. Since gotos & other jumps are verboten
in C, then maybe I should look at how it is structured.
Currently, I am reading a location in memory that is changed by an ISR (key_temp).
This portion of the program uses different keypresses to change the display of a LCD (and
eventually the data in the module).
I had been looking at it as a serial process, first check & change the months, when done
there, go to the next procedure of changing the days, hours, minutes, etc, etc.
Within each of these small chunks of program, there are ways to exit the code, for example
if the user just wants to leave & return back to the top of the program. The other is to jump
out of the date set, and go to another setting program called med_setup.
If I were to call each of these setting programs (month, day, year, hour, minute, am/pm) as
a function into themselves, each could return with a value that would say (wants to leave,
wants to do med_setup, go to next function, etc).
Within each function, I can do the proper updates, etc, by using the break; instruction &
no gotos - tnx!!.
But, once each function returns with a value that says what it wants to do, I am back into
the same problem of how do I go directly to a new function, without any kind of return back
to where it came from.
Tim