Why does ActiveTwoClient pad with zeroes?
Posted: Mon Sep 27, 2010 4:34 am
Hi,
I am not very familiar with Labview but from what I can determine the ActiveTwoClient tcp example pads the incoming numbers with zeroes at the least significant end. Why does it do this? Presumably it is creating a 32bit integer but by padding on that end isn't it creating a number that is 2^8 times greater than the number read from the socket? On the other hand if it padded on the most significant end it would cause problems with the negative numbers.
Could somebody explain what is going on?
Thanks
I am not very familiar with Labview but from what I can determine the ActiveTwoClient tcp example pads the incoming numbers with zeroes at the least significant end. Why does it do this? Presumably it is creating a 32bit integer but by padding on that end isn't it creating a number that is 2^8 times greater than the number read from the socket? On the other hand if it padded on the most significant end it would cause problems with the negative numbers.
Could somebody explain what is going on?
Thanks