Deallocation Issue in Ftypes

[rosenbrockc]

Deallocation Issue in Ftypes

[rosenbrockc]

Instead, stop caching the shared library DLL instances created by python in static_symbol. If we get a new library instance each time, it should have its own memory and then the current paradigm would work correctly. In that case, the overhead would move to the shared library loading. I don't see another way around this that doesn't involve double allocation of arrays in memory and copying values over.

[rosenbrockc]

For now, I decided to implement a full array copy to bypass this problem. It turns out that the ctypes library loading returns the same handle to each subroutine; loading the library again does not allow a separate block of memory to be allocated for the subroutines. This seems to be an inherent problem with the ctypes implementation and the fundamental differences between C and Fortran.

Andrew will look into creating a C++ wrapper to act as intermediary between F and C via ctypes. For now, revision 1.5.1 has the updates for safe memory access and deallocation by copying arrays lazily when a subroutine is requested an additional time. I will update this once he has looked into that.