What's the difference between boolexpr and Boolean types?

[chango]

Please don't say boolean is native and boolexpr is handle . I want a more in deep explanation if there is one .

Are these types interchangeable?

Thanks.

 

[Cohadar]

boolexpr is a pointer to a function that returns boolean

function test takes nothing returns boolean
    // ...
endfunction


local boolexpr b = Condition(function test)

 

[Tinki3]

And a boolean is either a true or false statement.

 

[chango]

Thank's !!

A very quick and easy explanation

Thank's a lot.

 

[Cohadar]

boolean is not a statement, it is a variable.
Statements can be of undetermined logical value.
Some may even be true and false at the same time.

but that has nothing to do with Jass... (unless you have desyncs in your map )

 

[Zouflain]

boolean is not a statement, it is a variable.
Statements can be of undetermined logical value.
Some may even be true and false at the same time.

but that has nothing to do with Jass... (unless you have desyncs in your map )

Eh? In physics things can be true and false at once (I forget what it's called, but two or more simultaneous quantum states until being observed ect/ect), but in programming (okay in JASS, GML and C/C++, as I don't know other languages) a statement is either true or false... unless I've missed something? A bit is one or zero, and a comparison between bits either returns that they are the same or different. At the core, all operations are in binary, so...

PS. Not sure - so don't quote me on this - but I've always heard that one should not destroy boolexpr's because they are automatically recycled. Only in certain circumstances should they be destroyed, and even then it's generally safer to just leave them alone as it's easy to introduce bugs by destroying them.

 

[chango]

Again,

Thanks for taking the time to answer this kind of nobish questions

Thanks

P.S.:


local boolean thisIsTrue = true
local boolean thisIsFalse = false

if(thisIsTrue == thisIsFalse) Then :nuts:


C ya

 

[Tinki3]

> boolean is not a statement, it is a variable

Yeah that's what I meant.
I must've been thinking of something like:

return IsUnitType(GetFilterUnit(), ...) blah

But yes, you're right, and I got muddled.