OPTv2: Over sensitive expression parsing

[Skrupellos]

While switching from Opt 2.0 to 2.1 beta, the expression parser has changed. Now it raises an exception if I write name="$basic@lte" text="$item.lte". The problem is the highlighted "lte" which is a keyword (and a mobile telecommunication standard). The same problem applies e.g. for "new", which is a common name for variables, imagine <opt:if test="$new">.

On the one hand, it clarifies the code if keywords are actually keywords.

On the other hand, its an unfamiliar behavior to forbid e.g. "new" in variables names if variables are marked as such (with a leading "$") for a PHP developer :-)

Therefore the question arises: Is it a bug or a feature to forbid such names as variable names?

[eXtreme]

Looks like a bug to me.

Please report your bugs to new bugtracker, hosted on Github https://github.com/OPL/Open-Power-Template/issues as we no longer maintain bugs.invenzzia.org
Please also move your FS#180 and FS#178 bug there, ok?