Re: Runtime KLIST change?

Hi guys,

let me say this: everybody of you knows how boring those discussions are and 
where they lead to.
I didn't want to discuss "the possibillity to use pointers to solve a special 
problem". I just
wanted a hint, if there is a possibillity and how it looks like. Believe it or 
not, but I'm also
doing programming for a couple of years and I think I could decide by myself if 
this solution is
practical and maintainable. If you don't know about those possibillities, how 
could you else
decide if its "good" or "bad" ??? :-)

greedzzzz,

Frank

boothm@earth.goddard.edu wrote:

> My gosh.  You are suggesting that one should not only write mystifying
> code, but then hide it so it can't be found be mere programmers?   Now,
> that is scary!
>
> "never seen a piece of unmaintainable code that was written with some
> kind of leading edge technology."    Let me mail  you a WSU program on 8" 
>floppy to look at.
>
> _______________________
> Booth Martin
> boothm@earth.goddard.edu
> http://www.spy.net/~booth
> _______________________
>
> Alan Campin <Alan.Campin@CaseLogic.com>
> Sent by: owner-rpg400-l@midrange.com
> 12/04/1999 09:39 PM
> Please respond to RPG400-L
>
>
>         To:     "'RPG400-L@midrange.com'" <RPG400-L@midrange.com>
>         cc:
>         Subject:        RE: Runtime KLIST change?
> ...
> Pointers usage, in my mind
> anyway, should always be encapsulated in a function and hidden. Using
> pointers in the general body of a program is scary to me and, of course,
> there is always that fear that someone will misuse a powerful tool.
> ...
> I have never seen a piece of unmaintainable code that was written with
> some
> kind of leading edge technology. Always the opposite. 2 or 3 thousand line
> mainlines with the same logic repeating 10 times in 10 different versions
> and one thousand line subroutines doing twenty different functions and all
> doing what could have been done in a few hundred lines of code if properly
> designed. Why engineer code when you can just start pounding code?
> ...
>
> Now that's scary.
>
> +---
> | 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
> +---

+---
| 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
+---