Re: *INZSR - I still love you!!!

Tony,

There are times, (when using the cycle), that *INZSR is extremely 
beneficial versus an EXSR.  Given that I suppose a person could have put a 
comment like (forgive spacing):
C*                        EXSR  *INZSR
Much as I don't use *ENTRY PLIST anymore but instead use a Procedure 
Interface and do the following
     D SKELETON        PI      *ENTRY PLIST
     D  Parm1                              like(something)
to facilitate searching for it.

Rob Berendt
-- 
"All creatures will make merry... under pain of death."
-Ming the Merciless (Flash Gordon)




CarollaT@xxxxxxxxxxxxxx 
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
01/13/2004 01:15 PM
Please respond to
RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>


To
rpg400-l@xxxxxxxxxxxx
cc

Fax to

Subject
Re:  *INZSR - I still love you!!!






IMHO, if there are tasks that need to be done at the beginning of the task
at hand, I simply code them at the beginning of the C-specs.  Perhaps this
is because I don't rely on the eternal repeating of the entirety of the
C-specs. 

I could see the enhanced 'neatness' of moving these 'initialization' items
to a subroutine, but beyond that, *INZSR simply adds to the 'mystique' of
the program, by not having to EXSR that initialization subroutine.  At a
glance, it forces you to first look towards the bottom of the code, or
search for the *INZSR text to see the program flow. 

Just my opinion.  Take it or leave it. 

Tony Carolla
MedAmerica Billing Services, Inc.
_______________________________________________
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.