RE: Using STATIC

Mark,

Joe Pluta and I disagree on this point.  Joe Pluta says it's fine, I think
it's poor programming design.

I think the extra steps should be taken to set up the variable in it's own
memory by using malloc or the like, Joe Pluta thinks it should be fine since
this variable will be residing in the CS (Code Segment) and not the stack.

It's a design issue, really, and if it's working for you now there is no
real compelling reason to change it if you are just doing it this once.  If
you plan on doing this a bit, you might want to do some research and
determine for yourself what the best method is.

Understand, what I am saying Joe Pluta thinks is actually what I think Joe
Pluta thinks and may be wrong.

Regards,

Jim Langston

-----Original Message-----
From: MWalter@hanoverwire.com [mailto:MWalter@hanoverwire.com]

Hello all,

I have been following this thread with allot of interest. I fixed my
previous problem in a service program by passing a pointer to a STATIC MODS
from a service program. From what I gather in your conversation, this is
BAD. Why? Don't get me wrong. I am not challenging your statements. I am
ignorant as to the proper and improper use of pointers.

I was trained as an RPG Programmer. I have never written any C or C++. I
taught myself VB and some JAVA. I do not have a Comp Sci degree. So could
someone please tell me why using the method that I used was wrong.


Thanks,

Mark