Do (And, Or, Not) reuse boolexpr in Jass?

[Luashine]

beginner friendly

/**
Always returns a new boolean expression that has the result of evaluating logical (NOT expr1).

@note Always returns a new boolexpr in Lua (v2.0.3.22988 and earlier) even when reusing previous `Condition`/`Filter`.
TODO: What about Jass VM? At least it reuses previously created `Condition`/`Filter`.

@note `boolexpr` extends from `agent` and must be explicitly destroyed with `DestroyBoolExpr` to prevent leaks.
However, most functions from blizzard.j destroy passed boolexpr automatically.
*/
native Not              takes boolexpr operand returns boolexpr

In Lua these functions don't reuse the previously existing filter/condition/and/or/not expressions and always create a new object. Please test this in Jass again, by supplying the same function twice and comparing them or their handle IDs.

1. Test: And, Or, Not
2. Share results here
3. Update jassdoc

[shuen4]

all 3 create new agent CBooleanAnd CBooleanOr CBooleanNot
parameter boolexpr operand is reused

[Luashine]

So even when operand remains the same, do they still create a new object on each call or not?

[shuen4]

still create new object