RE: Runtime KLIST change?

[Alan Campin <Alan.Campin@xxxxxxxxxxxxx>]

>> "The only good programs, regards of coding technique, are the ones that
>> work". No ones else's opinions ever could supersede such a statement.

My opinions only but I would strongly disagree. A program must work but what
is equally important, if not more important, is that it be maintainable. If
it works and you can't maintain it, it isn't worth much.

Study after study has shown that writing a program is only a fraction of the
total time spent on it in it's lifecycle. A vast majority (90% or more?) is
spent in maintaining the code. 

It has, also, been my experience that writing maintainable code has a
tremendous amount to do with writing correct code. If I have a function with
performs one function, has known inputs and known outputs and that logic is
in one place, how much easier is it going to be for me to test, prove and us
it than if I have the same logic repeated a dozen times in a dozen places
and I have to debug the entire program?

The program may work but how many hundreds of hours are going to be spent
trying to make changes to a poorly written program along with all the errors
that get introduced because of side effects. 

That is why I think that RPG IV and ILE are so important. If the first time,
we really have a hope of being able to write maintainable code! Question is,
is the RPG community going to rise to the challenge or just keeping saying,
"O Well, it runs. That's all that matters."

Guess that is enough ranting for now. 
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---