static if.....

[Arsenal]

At me such specific question - tell about the conditional operator "statics if" how and when is used? I just met a lot where I could not understand what is different from the usual "if". Thanks

 

[MyPad]

Static ifs are used such that at the flag's notice, it can change the behavior of your code.

For example, take Debug mode. You have functions that tell you what is happening as of the execution of certain parts of your code. When you disable debug mode, those messages do not appear. When enabled, those messages appear.

 

[nedio95]

Static ifs are used such that at the flag's notice, it can change the behavior of your code.

For example, take Debug mode. You have functions that tell you what is happening as of the execution of certain parts of your code. When you disable debug mode, those messages do not appear. When enabled, those messages appear.

This confused me a bit... are you saying they are executed during compilation time?

 

[Jampion]

This confused me a bit... are you saying they are executed during compilation time?

Yes they are.

In other words. If the condition is not met, the code inside it is ignored by the compiler.

 

[nedio95]

Yes they are.

In other words. If the condition is not met, the code inside it is ignored by the compiler.

I'm happy with this

@Arsenal boss of topic, you?

Regards
-Ned

 

[MyPad]

Well, the parts which pass the static if condition are retained. The rest go away.

E.g.

function foo takes nothing returns nothing
    static if DEBUG_MODE then
        call BJDebugMsg("Killing triggering unit")
    endif
    // If debug mode is true, the message will display.
    call KillUnit(GetTriggerUnit())
endfunction

 

[Cuore]

What are the differential characters of compile-time ifs (static ifs if you prefer) on one hand, and runtime ifs on the other?
(while I think I have a general idea of the meaning of the compile time vs runtime difference when it comes to errors, I'm not able to figure out precisely what the implications for if statements might be)

In other words, could you please explain in simple terms when is using static ifs advantageous over the usual ifs?
And conversely, could you name an example situation when you do NOT want to use static ifs?

Would this example I just thought at be a case where using static if would be appropriate?
static if: - a constant that I suspect is already defined at compile time exists -
then: - use the predefined constant -
else: - explicitly define a guess-value for the nonexisting constant, and use the guessed value for the rest of the code

 

[nedio95]

What are the differential characters of compile-time ifs (static ifs if you prefer) on one hand, and runtime ifs on the other?
(while I think I have a general idea of the meaning of the compile time vs runtime difference when it comes to errors, I'm not able to figure out precisely what the implications for if statements might be)

In other words, could you please explain in simple terms when is using static ifs advantageous over the usual ifs?
And conversely, could you name an example situation when you do NOT want to use static ifs?

Would this example I just thought at be a case where using static if would be appropriate?
static if: - a constant that I suspect is already defined a compile time exists -
then: - use the predefined constant -
else: - explicitly define a guess-value for the nonexisting constant, and use the guessed value for the rest of the code

Am, it is not exactly "static if" vs "regular if" as they are used for completely different things.
There is not really a comparison or advantage as they have very different purposes.
"static if" would be used to compile the code and you have

static if(conditions)
    compile code

and "if" would be to run the code and you have:

if (condition)
    logic & actions

Imagine the following for static if:

//This is a bizarre mixture between C & JASS syntax and some random custom simplified library, look the other way.

function ButtonDown takes nothing returns boolean
    static if (OS == Windows) //Static if for compilation
        if (Windows.mouse.position == positionOfButton) and (Windows.mouse.button1.buttonDown == true) //normal if for logic
            return true
        end if
    else if (OS == Android) // part of static if for compilations
        if (Android.screenTap.position == positionOfButton) //regular if for logic
            return true
        end if
    end if
    return false
end function

If we are using a Windows the code that would run would be:

function ButtonDown takes nothing returns boolean
    if (Windows.mouse.position == positionOfButton) and (Windows.mouse.button1.buttonDown == true) //Logical if
        return true
    end if
    return false
end function

The rest of the code (the android part) would not exist in what is ran.

You could by all means do the following, without static if, just normal if:

function ButtonDown takes nothing returns boolean
    if (OS == Windows)
        if (Windows.mouse.position == positionOfButton) and (Windows.mouse.button1.buttonDown == true)
            return true
        end if
    else if (OS == Android)
        if (Android.screenTap.position = positionOfButton)
            return true
        end if
    end if
    return false
end function

But now you have all this code that is compiled and ran. Each character takes space in your program and the OS check is also ran every single time the function is called, do you need this extra size and computations? No.


Hope this helps!
-Ned

Edit//I've noticed that I've done if(X = Y) instead of if(X == Y)

 

[IcemanBo]

You could make something like:

static if LIBRARY_UnitIndexer then
    do_some_indexer_things()
else
    do_some_not_indexer_things()
endif

.. to check if a certain library, like here library UnitIndexer exists in code, or not (or checking other constant booleans), and to arrange code as needed.
People for example use it to check if Table instead of hashtable could be used, EventRegistration things, etc.

 

[Arsenal]

How would it be digested now))

 

[IcemanBo]

Only one code block exists in the end, other one won't be compiled and be just thrown away. Example:

                static if not LIBRARY_TimerUtils then
                    set tmr = CreateTimer()
                    set table[GetHandleId(tmr)] = this
                else
                    set tmr = NewTimerEx(this)
                endif

The goal is to get a new timer. If TimerUtils exists, he gets a recylced timer from library TimerUtils ( using NewTimerEx())), and if ithe library doesn't exist the code line creates a new one.

You can do similar things for events you maybe want when a unit enters the world. If a UnitIndexer exists you can straight use the IndexEvent, but if not you have to create a new trigger.

It's used to have any lines of code, like maybe whole function blocks optionally compiled in code, as they are only needed if some conditions met. Otherwise I or remove them completly, or need to achieve the same goal with other code.