The problem with numeric labels is: 1) they are not self-documenting WHERE USED. The comment at the definition of the routine does not help you here.
2) There is not complier requirement that the labels be in order and more often than not, either through laziness or mistake, the labels get out of order. Any good editor has search capability (my favorite is UltraEdit) so locating the subroutine should not be a problem. Rich Taylor | Senior Programmer/Analyst| VERTIS 250 W. Pratt Street | Baltimore, MD 21201 P 410.361.8688 | F 410.528.0319 [EMAIL PROTECTED] | http://www.vertisinc.com Vertis is the premier provider of targeted advertising, media, and marketing services that drive consumers to marketers more effectively. "The more they complicate the plumbing the easier it is to stop up the drain" - Montgomery Scott NCC-1701 > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:owner-u2- > [EMAIL PROTECTED] On Behalf Of Kevin King > Sent: Tuesday, September 27, 2005 4:04 PM > To: [email protected] > Subject: RE: [U2] Good Programming Practice Question......... > > > 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: [email protected] > 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: [email protected] > 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: [email protected] > 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 > [email protected] > To unsubscribe please visit http://listserver.u2ug.org/ > ------- > u2-users mailing list > [email protected] > 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 > [email protected] > To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
