×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
So of course I had to ask myself, after Scott's comment, "Why _do_ I do it that way?"
Well, as it turns out it's based on a D-spec handout I got from a 2004 COMMON.
I guess it's one of those things that I learned then never thought to question.
Thanks for pointing this out.
-Kurt
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Scott Klement
Sent: Friday, April 01, 2011 5:30 PM
To: RPG programming on the IBM i / System i
Subject: Re: Constant arrays
On 4/1/2011 5:19 PM, Alan Campin wrote:
But that requires defining a length for ObjectTypes and overlays for
each element.
Kurt's example is actually identical to Jon's in the way it works. But I agree that Jon's code was much more elegant. I don't know why Kurt created the extra field, or why he overlaid it by hand.
Would be nice if IBM would just give use an INZARRAY keyword.
InzArray('*PGM':'*SRVPGM':'*CMD':'*FILE')
Ick.
What is your objection to the way Jon did it? Or if you don't like using a data structure, what is your objection to using CTDATA? I sure like CTDATA a lot better than the InzArray().
--
This is the RPG programming on the IBM i / System i (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.
midrange.com
