Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 579 by [email protected]: Spurious warning about conflicting
scalar and list base names
http://code.google.com/p/robotframework/issues/detail?id=579
I am encountering spurious warnings about scalar and list variables that
have the same name. Robot does not seem to be taking into account the scope
of the variable when checking for potential name conflicts.
To replicate:
1. Create a test case containing a list variable e.g. @{list}, containing
two values.
2. Create a user keyword with two arguments, one named ${list} and one
named something else.
3. In the test case, call the user keyword with @{list} as the argument.
The end result is that Robot complains that @{list} and ${list} conflict,
even though they are not in the same scope - @{list} is a local variable in
the test case, and ${list} is a local argument to the user keyword.
