polymorphism of "number to decimal string"

[GerdW]

Hi,

I'm in the progress of rewriting an older application. Here I found an interesting behaviour:

The "Number to decimal string" function should be polymorphic (as described in the context help). In fact it takes any scalar integer number without type coercion. But when I wire an I32 array (which is no problem in general) this function shows a coercion dot?!? This coercion dot is not shown in LV7.1...

So I'm questioning:

What is coerced here? To which datatype is the data coerced? May there some problems arise from coercion?

[smercurio_fc]

This had been raised by altenbach here.

[GerdW]

Thanks smercurio,

so this seems like a bug not solved by the 8.6.1 update...

[ghighuphu]

It is still not fixed in LabVIEW 2013 SP1.

Is there any post, where one could vote on it? Is there a CAR on it, please?

Cheers,

[Jeff-P]

Hi ghighuphu,

R&D is aware of this behavior, the CAR numbers are as follows: 

CAR 152789 - Coercion dot appears when wiring Integer Array to Number To  Hexadecimal String.vi

CAR 152788 - Coercion Dot appears when wiring Integer Array to Number To Decimal String.vi

CAR 152787 - Coercion Dot appears when wiring Integer Array to Number To Octal String.vi

Regards,

Jeff Peacock 

Product Support Engineer | LabVIEW R&D | National Instruments | Certified LabVIEW Architect