Hans, its not about saving an EXSR line.  *INZSR runs before one can EXSR. 

So far as putting the initialization lines up front...  I find nothing
useful about that concept.  I do not miss the old days when we had to wade
through dozens of lines of initialization code before we could see the real
program.  I want to see the mainline as soon as possible. Additionally I'd
really  prefer to have the initialization code off to one side where I can
review it separately..
 
 
 
---------------------------------------------------------
Booth Martin   http://www.MartinVT.com
Booth@xxxxxxxxxxxx
---------------------------------------------------------
 
-------Original Message-------
 
From: RPG programming on the AS400 / iSeries
Date: 1/13/2004 1:07:52 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: *INZSR - I still love you!!!
 
...
 
Maybe I'm just in a cranky mood today, but I'm not sure if saving one
(1) EXSR statement in the typical RPG program is enough of a reason to
justify having a special *INZSR name in the language. (Sure, there's
always RESET. But as I suggested earlier, I don't think much of RESET
either!)
 
As someone else mentioned, putting the initialization up front is
clearer than putting it lower down amongst the subroutines.
 
Cheers! Hans

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.