| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Re: History of BASIC and c |
From: "Geo"
"Antti Kurenniemi" wrote in
message news:43dcb7ff{at}w3.nls.net...
> Because it's almost impossible to trace back. If you have a place in your
> code where you can get from multiple GOTO's, you'll never know where you
> came from unless you write some funky trace-logic yourself.
If you modularize your code and only use goto's for local jumping there
should never be a problem like that.
When I would program in basic I used to create modules using gosub which
each returned to the control module on return. It was quite easy to track
back anything I needed with just a few pieces of tracking code.
The people who had problems with goto were the ones who didn't split their
programs up into managable chunks. Once a chunk of code gets too big to
keep in your head all at the same time it's time to give up on that code
and start with smaller chunks.
Geo.
--- BBBS/NT v4.01 Flag-5
* Origin: Barktopia BBS Site http://HarborWebs.com:8081 (1:379/45)SEEN-BY: 633/267 270 @PATH: 379/45 1 106/2000 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.