Storing variables in DLLs

[ewpatton]

I'm writing a DLL and want to store information internally between
calls to the DLL functions.

For example:

static int i1,i2;

INT APIENTRY StoreInt1(int i) { return i1=i; }
INT APIENTRY StoreInt2(int i) { return i2=i; }
INT APIENTRY GetSum() { return i1+i2 }

I have all the definitions set up correctly... and the test program
compiles fine... but when I run the program:

StoreInt1(5);
StoreInt2(10);
int i = GetSum();

i != 15?

It seems like after the application leaves the DLL it losses all the
static information so when it calls it again, the variables are fresh.
I've also tried making the whole library a static library (.lib vs
..dll) but the same thing happens.

Any ideas?

Evan

[Jack Klein]

On 8 Sep 2006 21:48:54 -0700, ew******@gmail.com wrote in
comp.lang.c++:

I'm writing a DLL and want to store information internally between
calls to the DLL functions.

[snip]

Then you need to ask in a group like
news:comp.os.ms-windows.programmer.win32, or one of Microsoft's groups
in the news:microsoft.public.* family. This is specific to your
platform and its mechanisms, the C++ language does not define or
acknowledge the existence of DLLs.

--
Jack Klein
Home: http://JK-Technology.Com
FAQs for
comp.lang.c http://c-faq.com/
comp.lang.c++ http://www.parashift.com/c++-faq-lite/
alt.comp.lang.learn.c-c++
http://www.contrib.andrew.cmu.edu/~a...FAQ-acllc.html

[Shark]

ew******@gmail.com wrote:

I'm writing a DLL and want to store information internally between
calls to the DLL functions.

For example:

static int i1,i2;

INT APIENTRY StoreInt1(int i) { return i1=i; }
INT APIENTRY StoreInt2(int i) { return i2=i; }
INT APIENTRY GetSum() { return i1+i2 }

I have all the definitions set up correctly... and the test program
compiles fine... but when I run the program:

StoreInt1(5);
StoreInt2(10);
int i = GetSum();

i != 15?

It seems like after the application leaves the DLL it losses all the
static information so when it calls it again, the variables are fresh.
I've also tried making the whole library a static library (.lib vs
.dll) but the same thing happens.

Any ideas?

Evan

---------------------------------------------------------

It seems like after the application leaves the DLL it losses all the

?? If your application stops refering the dll, the information is lost.
It should loose. Internally it maintains a reference count. once your
application stops refering it and no other applications are using it ,
even the dll gets unloaded. but even this doesn't matter. if you close
your application, the info would be lost. If you want to have them
stored for future usage, save them in a text file or use a db.