Re: Datastructure and Eval-corr question...

Robert,

If all fields in the data structure are the same names, sizes, positions, types, etc... then eval-corr will work identically to eval. I would not call it "overkill", since it will do exactly the same thing in that case.

However, if there are any differences, then eval-corr will discover that and will copy the subfields that match individually.

So, in my opinion, it's better to use eval-corr because it's always safe and will never screw up when the subfields don't match like eval does. There's really no advantage to coding the 'eval' method (aside from typing fewer characters when writing the code, I guess.)

-SK

On 8/20/2015 9:08 AM, Robert Rogerson wrote:

I have two datastructures

D detailDs e ds extname(dstopdp)
D detailSave ds likeds(detailDs) inz

If I code

/free
Read dstopdp;
detailSave = detailDs;
/end-free

then the entire detailSave datastructure is populated with the values
from detailDs. The same may be accomplished with

Eval-corr detailSave = detailDs;

So my question is if Eval-corr is meant to be used when some but not all
the fields in the datastructure are the same? Is using Eval-corr almost
overkill when both datastructures are the same and have the same fields?

Thanks,

Rob