Coercion the two different numeric data types（U8 and I8、U16 and I16、Ｕ32 and I32 ）make sense?

[jwdz]

We know：

       Coercion dots signify two different numeric data types wired into the same primitive.

—— Coercions in LabVIEW require data copies

—— Coercions involving large arrays are memory intensive

However, Coercion the two different numeric data types (U8 and I8, U16 and I16, U32 and I32) make sense?

                                              图1  No Coercion (U8 and U8)

                                         图2  Coercion Dots (I8 and U8)

                                      图3 Clear Coercion Dots (I8 and U8)

                                             图4 Clear Coercion Dots (U8 and I8)

                                 图5  Figure 1 to Figure 4 is the same amount of memory usage(2M)

In other words, even if there is data copying, and no increase in memory usage.

In this case, the Coercion Dots does not make sense.

U8 and I8, U16 and I16, U32 and I32 is the same.

Only for LabVIEW 2010

I'm sorry, my English sucks. Please Use simple sentence reply.

[jwdz]

Only for LabVIEW 2010.

[RavensFan]

Coercion does not mean there has to be a data copy.  Where did you see that?

Coercion means the data is being interpreted differently than what is coming in.  And I'd say U8 being coerced to I8, and so on, definitely applies.

[jwdz]

Accessories

Page 32

[altenbach]

Some easy reading:

View >> Gigantic Coercion Dots (now with a variety of colors)

Dealing with Coercion Dots