Type conversion for MATH results

[Controls Guy]

I want to check the presence of a certain bit in a DWORD.    I'm doing

Code: [Select]

MATH V619:0 "MyDword[idx] & BitMask"
...where BitMask is a DWORD with one bit in the position of interest.  I've often done that with an inequality (Stuff != 0), but I'm assuming that if I want to evaluate an expression as a boolean, the result will be true if non-zero and false for zero.   Is that right, or must I do an inequality in the expression string?   Couldn't find in MATH help where it addressed that.

[franji1]

I want to check the presence of a certain bit in a DWORD.    I'm doing

Code: [Select]

MATH V619:0 "MyDword[idx] & BitMask"
...where BitMask is a DWORD with one bit in the position of interest.  I've often done that with an inequality (Stuff != 0), but I'm assuming that if I want to evaluate an expression as a boolean, the result will be true if non-zero and false for zero.   Is that right, or must I do an inequality in the expression string?   Couldn't find in MATH help where it addressed that.

Sorry, since you are going to a BIT, it will evaulate 0 or non-zero as assigning 0 or 1.

[Controls Guy]

I think you're saying it's going to do what I want, could you clarify?

[franji1]

I think you're saying it's going to do what I want, could you clarify?

Sorry about that - yes it will do as you want.  When assigning a 32 bit integer or real to a bit, it evaluates zero/non-zero as 0/1.

Sorry for the confusion.

[Controls Guy]

Perfect, thanks!    That's what I expected but some preliminary results made me think it might not be evaluating that way.

You might want to add to the help how MATH handles differences between expression and result types.   For example, let's say the expression is boolean and the result is a number.   I assume it will do the same and assign 1 or 0 for TRUE or FALSE?  (can't conjure up a use case for that one, but that probably means I haven't run across it yet).

[franji1]

fyi, this behavior is in multiple instructions.  Any kind of value-based assignment (e.g. MOVE, MOVER, MATH, COPY, etc.) where the DESTINATION is a BIT, evaluates the FINAL SOURCE integer/real value of zero/non-zero and assigns 0/1, respectively.

There is no value TRUE or FALSE (but you could make 2 symbolic constants).

[Controls Guy]

fyi, this behavior is in multiple instructions.  Any kind of value-based assignment (e.g. MOVE, MOVER, MATH, COPY, etc.) where the DESTINATION is a BIT, evaluates the FINAL SOURCE integer/real value of zero/non-zero and assigns 0/1, respectively.

There is no value TRUE or FALSE (but you could make 2 symbolic constants).

Noted.    As far as TRUE and FALSE, I was using those for clarity in describing boolean/bit ON and OFF (or 1 and 0).   I know there's no predefined values with those names.

[Controls Guy]

Is there any speed/processor advantage to explicitly including '!=0', or to leaving it out?

[BobO]

Is there any speed/processor advantage to explicitly including '!=0', or to leaving it out?

Negligible, but less is faster.