If my DLL return an array, where do I free it?

I create a DLL, which return a structure

Code:

---

struct opStructure {
        int num;
        int **motif1;
        int **motif2;
};

---

The DLL allocates memory for motif1 and motif2, return opStructure to the program using this DLL. But how to I free this new memory of motif1 and motif2? I try to free this 2 memory in the program usinng this DLL but have error. Or I do not need to free them? DLL itself will free it??

When you return your pointer, you can free it using delete keyword. For every new keyword you use, there should be a delete pair. If you don't use new there is no need to free it.
Show your code for allocating an freeing memory.

Never free memory allocated in one module in a different module.

Three choices.
1) Pass in enough memory for the DLL to use, so that it doesn't have to allocate.
2) Create a DLL function that you pass the struct and it frees the memory.
3) Since this is C++, why not use a std::vector or a boost::multi_array instead of managing the memory yourself?

Quote:

---

Originally Posted by CornedBee

Never free memory allocated in one module in a different module.

Three choices.
1) Pass in enough memory for the DLL to use, so that it doesn't have to allocate.
2) Create a DLL function that you pass the struct and it frees the memory.
3) Since this is C++, why not use a std::vector or a boost::multi_array instead of managing the memory yourself?

---

This is the headache I'm facing. I'm allocating memory in DLL and freeing it in the program that is using the DLL. So far, it works alright. I agree it is risky, but for your first suggestion, I can't do it because the memory is dynamic, I will never know the exact memory size needed.

For your second suggestion, it's not possible because the if I free the memory in DLL, then my main program can't receive the array from DLL


For you third suggestion, I think it will have the first problem as the second suggestion

Below is my code which I call the DLL. minemqb is the DLL function. I'm passing in a pointer chain_interact_result, which the function minemqb will point it to the results I needed

Code:

---

minemqb(&chain_interact_result, db, protein[protein_index].chain[chain1][0]+1, protein[protein_index].chain[chain2][0]+1, 0, 2, 0, 2, 0);

---

No, you mustunderstood all three of my suggestions.

1) If the client allocates the memory, obviously the DLL needs a way of first reporting how much memory it will need.

2) If the DLL allocates the memory, it doesn't free it immediately. It frees it when the client calls a function that is explicitely documented to do that.
In other words, the function that returns the opStructure contains in its docs something like:
"The returned opStructure must be passed to FreeOpStructure when the client is done with it."

3) You're wrong. I don't know what else to say.

Quote:

---

Originally Posted by CornedBee

2) If the DLL allocates the memory, it doesn't free it immediately. It frees it when the client calls a function that is explicitely documented to do that.
In other words, the function that returns the opStructure contains in its docs something like:
"The returned opStructure must be passed to FreeOpStructure when the client is done with it."

---

Oic, I go and try it out now. When does the DLL free memory? When the client program cease? Or when the DLL function return control to the client program?

YES! it works! thanks cornedbee! Lesson learnt: The DLL only cease when the client program cease =)

The DLL frees (client specific) memory when it is unloaded either by (a) an explicit command to unload it, or (b) when the client exits.

what is the explicit command to unload DLL when my client program is still running?

In Windows? If you had used LoadLibrary()/LoadLibraryEx() to load your DLL, you'd use FreeLibrary() to release it (well reduce the ref count anyway). If you didn't explicitly load the library, you can't (safely) explicitly unload it. AFAIK