Updates:
Status: Accepted
Labels: Priority-Medium Target-2.5.5
Comment #1 on issue 728 by pekka.klarck: Errors with positional arguments
and arguments with default values
http://code.google.com/p/robotframework/issues/detail?id=728
The first case is by design. The named arguments can only be used as the
last arguments, and the current implementation doesn't even notice that
there's named arguments syntax somewhere else. Part of the reason to handle
this situation in this manner was that the whole named arguments syntax is
potentially backwards incompatible (you could have literal argument like
`arg=1`), and this way the places where backwards incompatibility could
occur were minimized. We could possibly show a warning (it's always
possible to escaping the named arguments syntax with `\` and get rid of the
warning), but I'm not sure is it worth the effort.
The second case is definitely a bug. In my opinion the result should be
that ${arg1} gets value `bar` and ${arg2} gets `arg1=foo`.
