|
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Jon Paris
Sent: Thursday, December 13, 2007 9:08 AM
To: rpg400-l@xxxxxxxxxxxx
Subject: 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
--
This is the RPG programming on the AS400 / 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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.