RE: Overlaying a DS Array In a LIKEREC DS

Not to pick on your preference, cuz I don't mind that method. However...

<snip>There is also the issue that when using Read with a result field I am
guaranteed that all fields are populated whereas using the technique
you describe the fields will not be populated if not referenced
elsewhere in the code.</snip>

That's not true, I use this method all the time and have never encountered a time when all the fields didn't get populated after a read.

Notice that in the DSPECS, I did not redefine how the fields are defined. So the program is using the fields from the file therefore they are being used in the program.

<snip>Well for one thing I hate using From/To notation - too error prone.</snip>

How is the example I gave too error prone. If the field sizes are identical, there's nothing to screw up. In this example position 1 is where field 1 begins. If you try to dim incorrectly the editor will tell you that it's wrong. Also that's what testing is for.



-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Jon Paris
Sent: Thursday, July 01, 2010 1:16 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: Overlaying a DS Array In a LIKEREC DS

Well for one thing I hate using From/To notation - too error prone.

Second - why would I want to go to the trouble of specifying all the
field names by hand if I don't have to?

Third, while I do use the technique of listing field names that you
describe, I tend to use it when the fields in question are not
contiguous and/or I do not need to use all the fields in the file.

There is also the issue that when using Read with a result field I am
guaranteed that all fields are populated whereas using the technique
you describe the fields will not be populated if not referenced
elsewhere in the code.


Jon Paris

www.Partner400.com
www.SystemiDeveloper.com



On Jul 1, 2010, at 1:00 PM, rpg400-l-request@xxxxxxxxxxxx wrote:

I suppose it doesn't matter... just not sure why you would want to
reference the external name CustData twice, once in the FSPECS, and
once in the DSPECS except to save on the amount of lines in your
source.