I second the motion.
Just throw everything into a pot and leave it to each person's taste.
I find some of the ideas suggested ludicrous but that's my opinion.
I generally prefer numeric labels (in strict sequence) with each label
meaning something. e.g. Label 800 is where every data entry program
goes after ALL fields are entered. Label 900 is the "Page Heading"
routine. Label 950 is the "Page Heading" routine if more than one
report is output.
These standards suit me and my employer. If they don't suit you then
that's your problem not mine!
I work on ONE system (currently HP Unix) running UniVerse
And I LOVE
LOOP WHILE READNEXT ID
Some code
IF needs be THEN CONTINUE ELSE EXIT
REPEAT
No EOF variables, no loop indicators. Self explanatory. No labels.
If you don't like it don't use it!
I have written entire programs without any labels and programs
with labels. You show me how you can write a data entry block
of code to allow entry of a field, validate it, allow the User the
option to accept it, "Go Back" to the previous field, abort the whole
session entered so far etc etc without labels. The input is really
done through an input handling subroutine which sets a return
variable after various validation routines. The return variable
is addressed by a ON R GO 300,100,800 etc.
Stop trying to impose YOUR standards on someone else. Just
express your opinion and move on.
My 3 cents worth.
Putting on flame proof suit.
Louis
----- Original Message -----
From: "Mark Johnson" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Friday, September 30, 2005 8:38 PM
Subject: Re: [U2] Good Programming Practice Question.........
: Kevin:
: It happened already. One poster said that subs should be 10 lines or less.
: That's his 'standard' and it works for him. It may not work for everyone.
:
: The back and forth on label nomenclature is another example. I use a
mixture
: of both numeric and alpha-numeric as my 'standard'.
:
: To answer your question, we all can contribute our own 'standards' and let
: the reader decide which standard will become theirs. In programming,
: especially in MV, there are many ways to solve the same problem. My
: standards may offend others as theirs may offend me. So the request for
: programming standards will inevitably cause conflict.
:
: I often get flames for my suggestions on this forum. That's fine. I'm used
: to it. I guess that as long as my standards work for me and my clients,
then
: that's fine also.
:
: I knew from the onset of that innocent question it would become a popular
: thread. Perhaps a compilation of the various methods for each MV element
: could be made (or acquired) and each could pick (no pun intended) what
they
: like the most.
:
: Thanks
: Mark Johnson
: ----- Original Message -----
: From: "Kevin King" <[EMAIL PROTECTED]>
: To: <[email protected]>
: Sent: Thursday, September 29, 2005 11:13 PM
: Subject: RE: [U2] Good Programming Practice Question.........
:
:
: > >This thread, while starting on noble grounds of 'good' programming
: > >practices, will eventually turn into a pissing contest of implied
: > >standards.
: >
: > I normally ignore you, but this one has me interested. Why must this
: > otherwise educational topic be degraded into implication?
: >
: > -K
: > -------
: > 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/
:
:
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
