Or(...) vs or

[Ezekiel12]

So, there is

native Or         takes boolexpr operandA, boolexpr operandB returns boolexpr

and the keyword "or". Are there differences between these two?

Same applies for And(...) and "and".

 

[Wietlol]

*Same applies for Not() and not.

 

[PurgeandFire]

The Or, And, and Not natives combine boolexprs (boolean expressions). The 'or', 'and', and 'not' keywords combine booleans.

I think Blizzard uses it to combine stuff occasionally during the GUI-JASS process. I don't remember 100% though.

 

[BPower]

You will not find too many uses for Or() and And(().
I only saw it once in GroupUtils.

 

[edo494]

And, Or, Not are very good if you have one(for not) or 2 boolexprs you want to execute back to back and dont want to suffer overhead from trigger creation and deletion. Other than that, they are useless garbage.

As PNF said, or, and and not work on booleans, so true, false, !=, ==, ... and Or, Not and And work on boolexprs, so basically on functions

 

[Dr Super Good]

If you can have boolexpr type global variables then you can use the natives for dynamic filters.

For example, you could apply filters from a boolexpr array with an accompanying size value. Filters could then be added, removed or re-ordered dynamically during a session.

Of course this could be done by evaluating the boolexprs into boolean variables and then using the appropriate in-built operators on them however those cannot be used as trigger conditions. As such the above native operators can be used to dynamically create trigger conditions (if JASS works as it should, which is often not the case).

Is it useful? Not really since the use case is probably very rare and can often be worked around about as efficiently.