My addition to this would be to use alphanumeric labels, and to *have* a main calling section. A main calling section that looks like:
GOSUB OPEN.AND.INIT GOSUB SELECT.FILE GOSUB PRE-PROCESS.VALIDITY.CHECKS GOSUB PRINT.INVOICES GOSUB UPDATE.FILES Looks so much better and is so easier to figure out than GOSUB 100 a bunch of statements a bunch of statements a bunch of statements GOSUB 1250 a bunch of statements a bunch of statements a bunch of statements GOSUB 1375 a bunch of statements a bunch of statements a bunch of statements GOSUB 4000 a bunch of statements a bunch of statements a bunch of statements GOSUB 9755 a bunch of statements a bunch of statements a bunch of statements IMNSHO - *=aee=* -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of George Gallen Sent: Tuesday, September 27, 2005 12:12 To: u2-users@listserver.u2ug.org Subject: RE: [U2] Good Programming Practice Question......... Also, how about a change log at the top of the program that lists, who, when and what/why a change was made. add to that a short description as to what the function of the program is for. * this program does ..... * * * date who changes made * date who changes made ******************************************** * George -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Dianne Ackerman Sent: Tuesday, September 27, 2005 2:57 PM To: u2-users@listserver.u2ug.org Subject: Re: [U2] Good Programming Practice Question......... I like these and would add another one - Add comments to tricky-looking code! -Dianne David A. Green wrote: ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
