Pekka Klärck

We already support the `$var` syntax in expression evaluated in Python (#2040) like ``` IF $var > 0 Log This is positive! ``` This is a special syntax that makes...

Extended variable syntax has some pretty important use cases like `${object.attribute}` and `${SPACE * 10}`. These need to have some equally easy alternative before removing the extended variable syntax can...

My point in the [earlier comment](https://github.com/robotframework/robotframework/issues/4674#issuecomment-1458282927) about `IF    $var > 0` was that this syntax should work the same way as nowadays (i.e. `$var` isn't resolved before evaluation) even if...

Very good question @manykarim. This is related to the following open design decision I mentioned earlier: > Should we limit variable base name to only alpha numeric characters and underscore?...

Making `$var` variable names more strict than `${var}` variable names would mean that the syntax is inconsistent. I don't consider that too big a problem in this case. Stricter variable...

@iot40-dp, `${var}` isn't always a string. When you use it on its own as an argument like ``` Keyword ${var} ``` the keyword gets whatever the `${var}` points to and...

One way to avoid the ambiguity with `$var` and `${var}` behaving differently in expressions would be disallowing using the latter. It would be a backwards incompatible change and would require...

Now that I look at this again, I have to say that I _really_ like the `$var` syntax. The example in the issue description is considerably nice than the same...

@MoreFamed I agree with pretty much everything you wrote. I'm not sure do we need to prohibit variables with names like `$3dogs`, though, but we certainly shouldn't allow variables to...

If you have a variable `${x}` that contains a string `1`, you can nowadays use `${x} > 0` and it works because Python will see and evaluate `1 > 0`....