Re: Style choices

As I said before, new code should be written as MAIN program. Why include
the cycle if you don't need it? And with a MAIN, *INZSR is gone. Your
startup routine is the procedure that you put on the Main Keyword.

Also, by careful with RESET. Reset stores a copy of whatever the value was
in static memory and you can end up with huge amounts of static storage
being used for nothing but storing regular defaults. CLEAR will reset
everything to defaults.

If you have a structure you can just declare a template in global and then
in your procedure just do a Inz(*LikeDs);

dcl-ds TD_MyStruc Qualified Template;
MyField1 Char(1) Inz('Y');
MyField2 Int(10) Inz(100);
end-ds

In procedure

dcl-ds MyStruc LikeDs(TD_MyStruc) Inz(*LikeDs);



On Thu, Sep 10, 2015 at 12:05 PM, <MichaelQuigley@xxxxxxxxxx> wrote:

One thing *INZSR will do for you that an INIT() function won't is set base
values for a structure. Using the RESET opcode will respect values you set
in *INZSR. A good practice to avoid the "magic" black-box feeling is to
put a comment with the RESET function. e.g.,

// Reset values to defaults in *INZSR
reset Structure;


I agree with Peter and Jeff. Using features of a language increases my
productivity. I tend to let the computer do whatever work for me that it
will handle--within reason. I work on one system where I let a programmer
(who reported to me at the time) get really deep in SQL joins with
COALESCE and CASE structures. The code is too obscure for general use, but
it was an *interesting* learning experience.

"RPG400-L" <rpg400-l-bounces@xxxxxxxxxxxx> wrote on 09/10/2015 09:37:29
AM:

----- Message from Peter Dow <petercdow@xxxxxxxxx> on Wed, 9 Sep

. . .
. . .
. . .

...If you know what something does, is it
still magic?

. . .
. . .
. . .

The way you insure you (and others who follow you) know what it does is
judicious comments where needed.
--
This is the RPG programming on the IBM i (AS/400 and 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.