Doh … of course you are correct Joe.

That’s what happens when you work through someone else’s approach iteratively instead of starting over - well that and old age!

As to your array situation I haven’t had any problems in that area so far but I’m guessing the answer is a group field defined with the Pos keyword. But how did you do it in fixed form?



On Mar 10, 2016, at 11:32 PM, Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx> wrote:

On 3/10/2016 3:30 PM, Jon Paris wrote:
I would go with Michael’s approach as the most efficient - except there is no need to define “string” as a field, simply name the DS itself as “string".

So my version would look like this:


D string DS
D array 1 Dim(37) Overlay(string)



You wouldn't even need the overlay, would you? I also have almost completely gotten away from H-. F- and D-specs. I much prefer using free-form declarations although they do present a challenge or two. :) I just figured out a new one: how to overlay arrays inside of externally described data structures (you know the ones - with lots of individual fields all in a row).

I'll be writing about that one. It was fun.
--
This is the RPG programming on the IBM i (AS/400 and 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.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Jon Paris

www.partner400.com
www.SystemiDeveloper.com


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.