Showing results for 
Search instead for 
Did you mean: 

64 bit Labview 2015 memory access

@richjoh wrote:


I don't think your following that LV "native host order" calls a function to determine the "host order". Same as you would do if your writing in C and needed to determine the endian. 

There is no need for that. LabVIEW is written in C(++) and gets compiled for each platform seperately. The Endianess of the target platform is known at compile time, so the code is written such that it does whatever is necessary for that target. No need to decide at runtime what platform its C++ written core is running on, as that can never change.


So when your VI runs, native will NEVER byte swap even if you run on a big endian machine, resulting in garbage data if the incoming data is little endian, little endian will byte swap when run on a big endian machine but not when run on a little endian machine and the big endian setting will do the opposite.

Rolf Kalbermatter
My Blog
0 Kudos
Message 31 of 31