LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Coercion dots in older LV versions

Solved!
Go to solution

Hello everybody,

I'm porting a program from LV5 to LV2016, I see that some values are coerced and I'm wondering if in LV5 the coercion dots where present or not to match the same result in the new application.

It seems to me that the usage of mixed data types worked differently in the older version (i.e. loosing the float part of a value when divide a double by an integer), is this possible?

Thank you

0 Kudos
Message 1 of 3
(2,612 Views)
Solution
Accepted by topic author v.minimo

Hi v.,

 

there are >10 years between your LabVIEW versions, with a lot of changes in the language and compiler. So you should expect several changes in your code - and coercion dots are just a minor issue…

 

loosing the float part of a value when divide a double by an integer), is this possible?

No. LabVIEW did the math right already in version 5…

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
Message 2 of 3
(2,600 Views)

Hi GerdW,

you're right, there are more than 20 years between the two versions...

I thought that maybe the coercion was not smart as it is in newer versions and the data were trunc in some cases.

0 Kudos
Message 3 of 3
(2,592 Views)