|
RE: prefixed commas . . are more readable , more understandable.
So in RPG, which do people think is more readable:
promptPrintForms(
rbcnppfUSER :
rbcnppfSSN :
rbcnppfSTDCD :
rbcnppfPKG :
rbcnppfID :
rbcnppfTXNO :
rbcnppfHCOR :
rbcnppfRESULT :
rbcnppfDO_ALL )
-or-
promptPrintForms
( rbcnppfUSER
: rbcnppfSSN
: rbcnppfSTDCD
: rbcnppfPKG
: rbcnppfID
: rbcnppfTXNO
: rbcnppfHCOR
: rbcnppfRESULT
: rbcnppfDO_ALL
)
This different format is not something that can be easily customized
inside your RDp editor,
but code-generators /and/ snippets might work well with this format.
The main thing is not to mix the two different styles within the same
section of code.
Make a logical break in the code if you are going to change the style.
- John Voris
from: Joe Pluta
subject: Re: RPG, open source, and the web
Henrik, . . .I must admit that I can see how the prefixed commas aremuch more
readily identifiable than postfixed ones, and I'm pretty sure I
assimilate them better. . . .
humanMihael, you may think I'm crazy bringing in LEAN psycologist into
programming, but just notise the "commas"
that is set in the front instead of the back in the above code - the
thebrain processes these commas in a
rate 3 times faster than if it was in the end of the statement if
code
yearsis hirachical structured - in 10 statements
you cannot hardly measure the diffence - but programmers during
has to
--read million of statements and suddenly
the time to mind- mapp code makes a difference.
This is the RPG programming on the IBM i / System i (RPG400-L) mailing
list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.