Re: Sharing Global Variables between Modules

If they are global, anything you change in one procedure changes it when used in any other procedure - so just forget about passing it.

Now you should be sure you have no undesired side effects - and passing as a parameter IS desirable.

Passing as a pointer - that is the same as it being global - you are changing values at a memory location - and that is the same everywhere, too. Bad idea - I think several have said not to do that on this list.

HTH
Vern

-------------- Original message --------------
From: "Coyle, Stephen F." <SCoyle@xxxxxxxxxxxxx>

Hi All,
I have 2 modules in a program. Each one /copies in a standard
3rd party data structure definition and it is not qualified. The DS is
global in each module. Each module can update the DS. I need to pass
this DS between modules and have any updates reflected in the calling
module.

Here is an example with I00SC as the global variable.
CALLER:
P5992101V1_AskEnv( Rec:I00SC) ;

CALLEE:
P P5992101V1_AskEnv...
P B export
D P5992101V1_AskEnv...
D PI
D Rec likeds(F5992101_t)
D XI00SC Likeds(I00SC)
/free
I00SC = XI00SC ; // initialize DS
....MODIFY I00SC HERE
XI00SC = I00SC ; // populate return DS
Return ;

There must be a better way than that. Passing a pointer around maybe?
An example would be appreciated.

Thanks...
- Steve



--
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.