|
Overlaying an array. D FLWORKREC DS likerec(flworkr) D pDuh s * inz(%addr(flworkrec)) D duh ds based(pDuh) D col 15p 4 overlay(duh:39) dim(389) Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin Hans Boldt <boldt@xxxxxxxxxx> Sent by: rpg400-l-bounces@xxxxxxxxxxxx 04/29/2003 10:59 AM Please respond to RPG programming on the AS400 / iSeries To: rpg400-l@xxxxxxxxxxxx cc: Fax to: Subject: Re: Adding another subfield to an externally defined data structu re. rob@xxxxxxxxx wrote: > Hans, > > What additional checking is done with LIKEREC that isn't already done with > EXTNAME? Don't they both pull in the field names and attributes? I > realize that once "you've let the cat out of the bag" by creating LIKEREC > it's hard to take it away. But if they do the same checking, I'd just as > soon use EXTNAME. > > Can you change LIKEREC so that we may add additional fields to it? Or at > least overlays? > > Rob Berendt Rob: As I suggested, one of the design features of LIKEREC is that you can't add subfields to it. Thus, it can be used as the result of record I/O with confidence that the data structure matches the record precisely. Do you want to be able to read into a data structure that does not match the record? What exactly are you trying to accomplish? Cheers! Hans _______________________________________________ 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.cgi/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.