VI inlining changes error message!?!

[Götz Becker]

Hi,

I was trying to track down a strange error in a library function and got the following:

For debugging I had to disable VI inlining and the error changed in something more meaningful:

Basically the problem was a parse error resulting in a wrong variant to data conversion (path to i16).

I wonder who is "Akash B" and "Stephen M". About the latter I have a guess .

[Aristos Queue]

Hi,

I was trying to track down a strange error in a library function and got the following:

For debugging I had to disable VI inlining and the error changed in something more meaningful:

Basically the problem was a parse error resulting in a wrong variant to data conversion (path to i16).

I wonder who is "Akash B" and "Stephen M". About the latter I have a guess .

That has been fixed in LV 2011. As you may guess, someone whose name is *not* in that error message decided to use index zero. That someone has been made to apologize deeply.