Re: Multi- Occurrence Data Structure

On 13-Dec-07, at 6:22 AM, Ken Sims wrote:

As I
was putting the array index on the statements loading the various
sub-fields, I thought "Why the hell am I doing this? I'm not going to
be sorting it or doing anything else which needs the array
functionality."

I can tell you why I would have done it - because it would make it obvious to those reading the code later (me included) _exactly_ which value (from the set represented by the array/MODS) was being used by the instruction. That simple piece of knowledge - which would save me time over and over again in the future - far outweighs any trivial benefit from the few seconds I saved by not having to type the subscript.

For example if using a DS for before/after images of a record and I see this code:

If myRecord(before).custType = retail;

I know exactly which field is being referenced. Which one is this referencing?

If custType = retail;

To me it is that simple.

In programming I don't want to use new features simply because they are new, but if - as in this case - they offer significant improvements in readability then I think adoption of the new technique is the right way to go.

Jon Paris

www.Partner400.com
www.SystemiDeveloper.com