You could use CVIDynamicMemoryInfo() to see the before and after state
of allocated memory. You can also view the code for ListDispose() under
..\CVI\toolslib\toolbox\toolbox.c if you are concerned about something
not getting cleaned up correctly.
Thanks for your response. I would like to be able to check the variable
to determine if it has been disposed. Having looked in the source,
setting the value of the ListType variable to zero after calling
ListDispose can accomplish this. Because ListDispose only frees the
memory occupied by the list and does not modify the value of the
ListType varialbe, it is possible to generate errors by accessing a
list that ListDispose has been used on. I will set the list to zero
after ListDispose, assume the memory was freed successfully, and check
that the list is not zero every time I access it.
I was just needing to use this today and I finally noticed that as Zyptron points out, unlike the behavior of most other free( ) type functions, the debugger doesn't show 'Invalid: freed' when you call ListDispose( ). Why is that?