JKSH wrote:
So labview.lib is deprecated in favour of labviewv.lib. Is this documented anywhere?
I wouldn't call it depreciated really. It will work in most of the cases just fine, except in the corner case where someone writes a LabVIEW VI DLL that makes use of the C DLL you link with labview.lib and someone else wants to link in this LabVIEW VI DLL into a different version of LabVIEW.
It's not an impossible situation but rather unusual as it is quite a roundabout way of doing things. Much better would be in this case to abandon the LabVIEW VI DLL altogether and use the original LabVIEW VIs that were used to create the DLL. Much easier to maintain, debug and also gives LabVIEW the possibility to optimize various things. With a DLL interface LabVIEW has ABSOLUTELY no way of optimizing anything, and generally the datatypes passed to the DLL have to be standard C type compatible, which often requires additional overhead for converting them from LabVIEW to Standard C and back to LabVIEW. (If you use LabVIEW native datatypes for the LabVIEW VI DLL interface you limit the DLL to be only usable from within LabVIEW, which is really überstupid to do, as using the VIs directly still would give you much better debuggability and code maintenance).
That all said it is documented although not with as many words in the online help for LabVIEW Reference where they simply recommend to link with labviewv.lib without anymore mentioning anything about labview.lib.