|
That's true, CTDATA must be global to the module. That's one
disadvantage to it.
There's no problem with referencing CTDATA in a procedure -- it's no
different than referencing any other global variable in a procedure.
But I do see the disadvantage of it being global. Thanks for reminding me.
That's not a problem with INZ, though... you still haven't told me
what's wrong with Jon's technique?
On 4/1/2011 5:41 PM, Alan Campin wrote:
Unless I am mistaken CTDATA has to be defined globally meaning defining--
static storage. An INZARRAY or
defining like I did means it is defined locally. Also didn't I read you
cannot reference CTDATA in a subprocedure?
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.
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.