Support Board

Date/Time: Fri, 03 May 2024 09:35:18 +0000

Post From: Dynamic Memory Allocation

[2014-05-06 11:17:01] Link To Thread - Link To Post [Go To First Post]
wwwingman - Posts: 185
Since the problem is now identified as related to the DLL unload/load architecture and persistence of data between events in case of an unload, it means we MUST rely on Sierra persistent vars/data block or on another persistence mechanism we add/make. It also means the problem is not related to Visual Studio and that the fact that data is not destroyed with MinGW should be considered as accidental. If of interest, I am considering this for persistency (since the SierraChart Persistency vars is not enough for my needs) : http://channel9.msdn.com/Blogs/Interoperability/Redis-on-Windows-Getting-Started Again thank you. W. Date Time Of Last Edit: 2014-05-06 18:53:44