#4 Invalid Assignment in Library Call

[Charlie]

I don't know if this is a real bug or not, but if you initialize a Real variable in a LibraryCall to an integer value, the type seems to get set as Integer, and a subsequent assignment of a Real value to it will throw an invalid assignment error.

Consider the following code:
File 1

LibraryNode Simple1(InOut Real current);

LibraryCallTest:
{
NodeList:
{ LibraryCall: Simple1(current=2000); }

}

File 2

Simple1:
{
InOut Real current;

NodeList:
GetInits:
{
NodeList:
SetCurrent:
{
Assignment: current = 0.1;
}
}
}

When the assignment in File 2 is reached, an error is thrown. This is using version 1.0.

This should be low priority, as it can be avoided by simply adding ".0" to the integer value.