Re: Advanced Programming Structures

["Rick Cortese" <ricortes@netmagic.net>]

"Robert S Ely" <rsely74@optonline.net> wrote in message
3B46F93E.F922450F@optonline.net">news:3B46F93E.F922450F@optonline.net...
>
> 570 REM [some small code to do something]
>

600 RETURN
> .
> .
> .
>>> 1530 if x=y GOSUB 572
>
> Now this may look like a procedure call or a sub routine, but it may do
some specific task that can't be done as a specific
> routine call. I don't happen to have any examples on-hand at the moment. I
call this glue code to stick program parts together.
> It's rare, but necessary at times.

Subroutines, even in Atari BASIC vs XE BASIC, should work and be a bit
easier to translate into other languages.

I've always found starting to write a program as almost an outline of what
you wanted to accomplish then filling in the routines later works well to
structure a program. I will start off with things like the first 5 lines
something like.

10 GOSUB INITSCR
20 GOSUB INITHARD
30 GOSUB FLOPPYIO
40 GOSUB ALTCHRSET
50 GOSUB MAIN:END