> Another way to organize the code is to have various blocks of code each
> terminating in a GOTO back to some point in the program loop. Just
> branch to the proper block and it knows the way home.
>
> You could also put a bunch of GOTO X1 GOTO X2 ... at the front of the
> program - basically a jump table. Even if the destination changed from
> programming mods, the location the the GOTO statement would not. This
> would simplify using the Y command.
>
> Richard
>
>
I have found that branching to subroutines is fine when most of the
oopic is programmed as virtual circuits. In this way any number of
subroutines can be branched to as long as a previously 'branched to' sub
has executed before the next branch command is issued. An acknowledge
string can be sent at the end of each sub if need be. Using Ack.debug at
the end of a sub, where Ack is a declared byte variable, puts the string
"Ack=0" on the USART Tx without the need for any serial object.
To eliminate the confusion/difficulty of finding the correct address for
a sub-routine, I have updated my original Sub Address Finder
(executable) which will now work with the .OPS files generated by the
ver 6 IDE/Compiler. I will place it in the files section later today for
anyone interested in using it.
Ian
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/oopic/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/oopic/join
(Yahoo! ID required)
<*> To change settings via email:
mailto:oopic-digest@yahoogroups.com
mailto:oopic-fullfeatured@yahoogroups.com
<*> To unsubscribe from this group, send an email to:
oopic-unsubscribe@yahoogroups.com
<*> Your use of Yahoo! Groups is subject to:
No comments:
Post a Comment