new comparison operators and logic constraints

[dsnz]

I propose two basic missing and trivial capabilities

1. addition of <= (less than or equal) and >= (greater than or equal)
comparison operators

2. addition of fixed literal constraints true and false
(this helps mainly to create a while true loop)

3. add as constraint the value of a variable (boolean or numeric/string; for numeric true is any non zero value, for string true is any non empty string)

 

[Abalsam]

I propose two basic missing and trivial capabilities

1. addition of <= (less than or equal) and >= (greater than or equal)
comparison operators

2. addition of fixed literal constraints true and false
(this helps mainly to create a while true loop)

3. add as constraint the value of a variable (boolean or numeric/string; for numeric true is any non zero value, for string true is any non empty string)

For the first, the existing not > is the same as <= and the existing not < is the same as >=. For the second, you can do this already by testing the value of a variable. For example have an action calculate the new value of a boolean variable at the end of the loop. For the third, you can do an action to assign true or false to a boolean variable based on the criteria described.

Therefore, since you can already achieve the same outcome today, what would the new requested functionality provide?

 

[dsnz]

for the first , I have to write a bad negated constraint, the fact that can be done does not mean that a better construct should be avoided (damn, all programming languages have these operators, even Fortran )
same holds for the second , why create a dummy variable and pollute my variables , it's much easier to have a true/false literal or a true/false magic text
again same for third (doing a quick test as described rather than a whole "if" to assign a variable is simpler and preferred, think Python etal. - for booleans this exists already but could be provided and for other types too)

finally booleans cannot be compared directly (4th ), again I must create an integer variable (!) with the result of comparing booleans and then test it (!) too much and advanced for most users