Re: free form alternatives?

["Joep Beckeringh" <joep@xxxxxxxxxxxxxxxxxxx>]

I realise that my previous statement might be interpreted as if I was
talking about compile time, but that was not what I meant.  What I meant was
that recent models of the AS/400 oops eServer Iseries have become so fast,
that views on performance have changed significantly.  That programs should
be easy to read and understand has always been higher on my priority list
than performance, but on the newer models performance is hardly an issue any
more.  It is only in long running batch programs that process hundreds of
thousands or millions of records that the effects of optimization become
noticeable.

And for 'bad code': in my book that stands for incomprehensible code.

Joep Beckeringh


----- Original Message -----
From: <nb@unitessile.it>
To: <rpg400-l@midrange.com>
Sent: Tuesday, September 25, 2001 11:50 AM
Subject: Re: free form alternatives?


>
>
> >> No, I am not really worried about the difference in cost between MOVE
and
> %editc.
> Well, of course i wasn't talking about compile time, which should be
performed
> just one time (or several, depending on error you find, but always an
irrilevant
> nuber of time comparing to execute times) but about resource (es. CPU
time)
> during execution of program. If you need to execute the %editc() statement
some
> hundred of thousand times in you app, you may end with a longer executing
> program, which will end with you user wait for the app end.
>
> Of course, by your previous statement, you seem to 'suggest' to write bad
code
> (i.e. not try to optimize code) and, if you AS won't execute it fast,
well, just
> buy a bigger one....