Currently the following two parameter names are reserved:
or - This parameter name is restricted for command script expressions.
and - This parameter name is reserved, though not used anywhere, yet.
The reason is that those cannot be clearly distinguished currently from the existing operators. Command script example:
[commands]
build = "echo %{value 'one' or 'two'}"
The value here is an actual parameter value passed in, where or is the keyword.
Proposal
It should not be necessary to reserve those names. This would also make more issues in the future if there would be more keywords. So those should either be:
Different names (e.g. chars like & and |)
Function names (#24 like either(value, 'one', 'two'))
Description
Currently the following two parameter names are reserved:
or- This parameter name is restricted for command script expressions.and- This parameter name is reserved, though not used anywhere, yet.The reason is that those cannot be clearly distinguished currently from the existing operators. Command script example:
The
valuehere is an actual parameter value passed in, whereoris the keyword.Proposal
It should not be necessary to reserve those names. This would also make more issues in the future if there would be more keywords. So those should either be:
&and|)either(value, 'one', 'two'))