unexpected token

[Matthew_Kelton]

I have run into a problem where TestStand is reporting an unexpected token and I don't see why.  In the attached image I am trying to map a number to SignalRouting.  TestStand claims that Signal is an unexpected token.  It is the only item in the container I cannot map to correctly.  I am trying to pass a LV U16 enum into it.  I don't seem to have this problem with any other enums.  Any ideas?

LV8.5, TestStand 4.0.1




Message Edited by Matthew Kelton on 03-26-2008 02:23 AM

Message Edited by Matthew Kelton on 03-26-2008 02:26 AM

[Matthew_Kelton]

So, if I do not use the name Signal for the container name, then TestStand doesn't give me this error.  I also have a similar container named Interferer which also gives a similar unexpected token error.  Again, if I don't use the Interferer name for the container, then it works fine.

I think the problem is that the enum for SignalRouting has Signal and Interferer as values.  The other option is Both, and if I name the container Both, then TestStand complains about the unexpected token.

Is there some rule you can'have have the name of a conainter containing an enum be a one of the value s of the enum!?  Or is this a TestStand bug?

[Jimmy_Reumuth]

This is a bug in TestStand. I have created a bug report (ID 100053) for this. This will happen any time you use a variable that has the same name as an enum value with an enum parameter.

Even though you get an error at design time, if you ignore this error there shouldn't be any harmful side effects at run time.