int pointer to a long int???

In order to make my code faster, I'm utilizing an option of a DLL
function to save a state internally.

I'm using a DLL function w/ following prototype:

Code:

---

int SOMEFUNCTION(double this, void that, . . . , int *phandle)

---

The handle allows for internal state to be saved but I am really
having trouble with syntax and a concept. In the description of
the parameters phandle it says:

Quote:

---

. . . it is necessary to pass a pointer to a long integer for
phandle. phandle will store a handle that is used for each
following call to SOMEFUNCTION. Call SOMEFUNCTIONCLOSE
when done.

---

I've tried various approaches, but none have worked. I did get it
to compile once with the following:

Code:

---

int *phandle;

for (blah blah blah){

.
.
.

iReturn SOMEFUNCTION(stuff, . . . , phandle);
.
.
.

}//end for

SOMEFUNCTIONCLOSE(phandle);

---

Once I ran the code above I got a runtime error that phandle was
not initialized. What value should I put in phandle? I think that
my problem is that I am not understanding how to set ". . . a
pointer to a long integer. . . "
Could someone please help me understand what they mean?

Also one more question, this for loop is executed many times. Is
it necessary to declare this pointer outside of the scope of the for
loop in order for the state to be "saved?"

Thanks for your time.

All it's saying is that it wants a pointer to an integer. In your example, phandle pointers to nothingness.

Code:

---

void foo(int *phandle)
{
    //...
}//foo

int main()
{
    int handle;

    foo(&handle);

    return 0;
}//main

---

gg

Since it specifically says that phanlde must be a pointer to a long int shouldn't it be like this?

Code:

---

int main()
{
    long handle; // or long int handle;

    foo(&handle);

    return 0;
}//main

---

>> int SOMEFUNCTION(double this, void that, . . . , int *phandle)
Use the same type that the prototype uses.

gg

Quote:

---

Originally Posted by Codeplug

>> int SOMEFUNCTION(double this, void that, . . . , int *phandle)
Use the same type that the prototype uses.

gg

---

sorry

didn't look at it too closely just noticed this

Quote:

---

. . . it is necessary to pass a pointer to a long integer for
phandle. phandle will store a handle that is used for each
following call to SOMEFUNCTION. Call SOMEFUNCTIONCLOSE
when done.

---

If the description and the code differ, then the code is "right", but most likely buggy (in that it doesn't conform to the description, or is not portable, or whatever). Or the description is just plain wrong.

Code:

---

int SOMEFUNCTION(double this, void that, . . . , int *phandle)

---

In this case, I think there is a fair chance that the code is not right. :D

by using this and that. . .
I simply did not want to confuse the pointer at hand ;)

The code and function prototype are correct, but I think that
there is an error in the descriptions. I did not consider this as
a possibility when trying to implement it. I'm just not well-
equipped or confident enough to go pointing fingers (yet).

Thanks, I'll try these changes suggested by Codeplug

What about the last part of my post??? Anyone have an answer
to my scope question? :confused:

If the variables is declared inside the for block, then its value will be 'lost' for each repetition of the loop. So yes, it needs to be declared before the for loop.