Re: Why COBOL is losing the POWER struggle
- From: "Pete Dashwood" <dashwood@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 24 Jun 2009 11:55:21 +1200
Howard Brazee wrote:
On Tue, 23 Jun 2009 13:15:06 +1200, "Pete Dashwood"
<dashwood@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Sometimes someone has a reason for his preferences - other times, it
is just taste. Nothing wrong with the latter. But do you have a
reason to prefer one line?
The less code I write, the fewer errors I make.
OK.
But for me -
The fewer shortcuts I take, the easier it is to figure out what I
wrote.
Also, since this is a CoBOL group - we have all come across
abbreviation problems, trying to remember whether the variable is
ACCT-NBR or ACCTNG-NUM. I make fewer errors typing it out.
Yep. Many times. That's why I love Intellisense... it won't let you make
those mistakes and if there is ambiguity, it spots that too and makes you
choose. It does the same with procedure (Method) names, even popping up a
prototype of what parameters are required and their datatypes, whenever you
reference them. How often have you written a PERFORMed routine then not been
quite sure what you called it? No more... Visual Studio rules...
In CoBOL, there is more typing in typing END-IF as opposed to typing a
period. I suspect there are fewer errors with the former.
I'd agree. But if the IDE can type "end-if" for me then it isn't a problem
is it?
Admittedly, you are comparing CoBOL with other languages - which I can
do too - how about the very concise RPG?
Yeah, how 'bout that RPG? Reckon they'll take the Rose Bowl this year... :-)
Nah, for me, I don't find a strong correlation between less code and
fewer mistakes - for the same desired result.
Because you correct the mistakes in the debugging and testing phases of your
development.
"fewer mistakes" Is not the ONLY reason I prefer concise code, but it is a
major one.
(Another reason is that it is quicker to read and pick up what code is doing
if it was written by someone else, when there is less of it.)
Pete.
--
"I used to write COBOL...now I can do anything."
.
- Follow-Ups:
- Re: Why COBOL is losing the POWER struggle
- From: Howard Brazee
- Re: Why COBOL is losing the POWER struggle
- References:
- Why COBOL is losing the POWER struggle
- From: Pete Dashwood
- Re: Why COBOL is losing the POWER struggle
- From: riplin
- Re: Why COBOL is losing the POWER struggle
- From: Pete Dashwood
- Re: Why COBOL is losing the POWER struggle
- From: riplin
- Re: Why COBOL is losing the POWER struggle
- From: Pete Dashwood
- Re: Why COBOL is losing the POWER struggle
- From: Howard Brazee
- Re: Why COBOL is losing the POWER struggle
- From: Pete Dashwood
- Re: Why COBOL is losing the POWER struggle
- From: Howard Brazee
- Why COBOL is losing the POWER struggle
- Prev by Date: Re: Why COBOL is losing the POWER struggle
- Next by Date: Re: Why COBOL is losing the POWER struggle
- Previous by thread: Re: Why COBOL is losing the POWER struggle
- Next by thread: Re: Why COBOL is losing the POWER struggle
- Index(es):
Relevant Pages
|
Loading