How the Threads of TestStand treats the global variables of a CVI DLL

[rrossi]

I have been searching about this issue but I couldn't find some official documentation or white paper of NI explaining clearly how the threads of TestStand treat the global variables declare in a CVI DLL. I would be very grateful if someone could explain this.

Also I would like to ask what are the best practices in this cases.

Thanks in advance.

Ramiro Rossi.

[GuenterMueller · Accepted solution]

I hope you like this thought: You can call your CVI DLL from many types of code. The DLL will not know who is calling, so the answer must be specific to a DLL, not TestStand.

As you know from C, global variables keep the value that has been recently written to them and this is also true if the caller is TestStand - multi-threaded or not.