Re: Classic Traps -- I need your input!

Nothing wrong with subroutines. If you have *INZSR or *PSSR, you can't
convert those to procedures. Also, any subroutines with a RETURN in them
will only exit the subprocedure when they are converted, and not return to
the calling program, as was intended, meaning you'll have to rewrite the
logic.

On Mon, Mar 31, 2008 at 10:46 AM, Steve Richter <stephenrichter@xxxxxxxxx>
wrote:

On Sun, Mar 30, 2008 at 6:48 PM, Scott Klement <rpg400-l@xxxxxxxxxxxxxxxx>
wrote:

Folks, I'm working on an article that's tentatively titled "Classic
Traps and How to Avoid Them". The general idea is to discuss the classic
mistakes that programmers make while programming, and (where necessary)
explain how to avoid that.

using subroutines instead of sub procedures. using global variables for
anything other than maintaining state between program calls ( and even
that
is problematic more often than not. Better to store the state in the
program
caller and pass it as parms to the program. )

global variables and subroutines were necessary because the system has
historically been underpowered by the IBM marketing division. Based on
Chris
Maxcer's reports of what IBM is announcing this week. i5/OS may finally
get
price/performance parity with the system p.

http://blogs.systeminetwork.com/isnblogs/maxedout/2008/03/shearer_throws_down_at_the_com.html#comments

-Steve
--
This is the RPG programming on the AS400 / iSeries (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.