I personally would rather use alpha-numeric labels because of the many programs I have come across that tend to not have comments. You can always use a locate to find the subroutine especially if you use correct labeling with a colon at the end. END.OF.PROGRAM:
----- Original Message ----- From: "Kevin King" <[EMAIL PROTECTED]> To: <u2-users@listserver.u2ug.org> Sent: Tuesday, September 27, 2005 3:03 PM Subject: RE: [U2] Good Programming Practice Question......... And here's where the conflict begins. When looking through a big program, I much prefer numeric labels in order with comments vs. alphanumeric labels. With numeric labels in order you find 1800 and if you're looking for 2000 you know to look farther down, 1000, go up. With alpha labels if you find SELECT.FILE and are looking for UPDATE.FILES, you have nothing but experience to know whether to look up or down from there. Numeric labels are good. Not ordering or commenting them is bad. And not putting comments around all labels to make them more easily distinguished from the rest of the program is near unforgiveable. -K -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Allen E. Elwood Sent: Tuesday, September 27, 2005 12:40 PM To: u2-users@listserver.u2ug.org Subject: RE: [U2] Good Programming Practice Question......... 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/ -- No virus found in this incoming message. Checked by AVG Anti-Virus. Version: 7.0.344 / Virus Database: 267.11.7/112 - Release Date: 9/26/2005 ------- 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/