Does an 'If' inside a macro get compiled-in if false?

[OgreVorbis]

For example (pseudo code)...

Code: Select all

Macro DrawClock(x, y, hand, hand2, hand3, enableThing)
	Line(...)
	Line(...)
	If enableThing
		Line(...)
		Line(...)
		More stuff...
	EndIf
EndMacro

Does that produce the code with the If statement compiled in, but it always skips if enableThing is false, or is the if statement not even compiled? Like it never existed?

I have a design question also. I'm writing a program that draws a clock on the desktop (fully animated analog) and as such, it needs to consume as little CPU as possible. I want to make sure it does not send the CPU into a high power state, so far it's good. There will be several different options for clocks. The most comprehensive way to make it would be to have an array of structures, one for each clock, and then pass that specific array element to a DrawClock Procedure. This seems nice code-wise, but for efficiency, I thought using a Macro for drawing the clock inside of a switch case for each different clock might be more efficient. What do you think?

[jacdelad]

The macro has no effect on the power consumption of your program. The code inside the macro is placed at the point where the macro is called. Think of it more as a way to slim down your code instead of writing the drawing routine for each click separately. Plus you don't have to change each one of them if the code is updated.

[OgreVorbis]

The macro has no effect on the power consumption of your program. The code inside the macro is placed at the point where the macro is called. Think of it more as a way to slim down your code instead of writing the drawing routine for each click separately. Plus you don't have to change each one of them if the code is updated.

Yeah, I know how it works. I'm just saying that if I use a procedure instead, it has to use the stack and structures and maybe other things internally.
So I think the macro would very slightly reduce the CPU cycles of the program (over a proc with a struct).

The main question has not been answered though. If you don't know, that's cool, I'm just pointing that out if someone wants to answer.

[STARGÅTE]

Does that produce the code with the If statement compiled in, but it always skips if enableThing is false, or is the if statement not even compiled? Like it never existed?

The macro inserts its content at the position of its call, while all parameters are replaced.
This means, the If-block is always compiled and "enableThing" is replaced by the parameter you passed during the macro call.
If you pass #False, the If-block is compiled anyway, because If is a runtime keyword.
It would result in "If #False" and the code is compiled but not executed.

When you write a macro like:

Code: Select all

Macro DrawClock(x, y, hand, hand2, hand3, enableThing)
	Line(...)
	Line(...)
	CompilerIf enableThing
		Line(...)
		Line(...)
		More stuff...
	CompilerEndIf
EndMacro

then the code inside the CompilerIf block is only compiled, when enableThing is #True during the compilation.

Two the second question: "I thought using a Macro for drawing the clock inside of a switch case for each different clock might be more efficient. What do you think?"
No. All drawing commands are much more time consuming than a little procedure call. Macros would not help.

[mk-soft]

You should work with structures and create a separate memory area for each clock.

Or immediately as OOP

Link: Own Flat Gadgets as Object

[OgreVorbis]

That answered the question perfectly. Thanks.
And I didn't think about the ratio of time spent in drawing vs. my procedures and stuff. Clearly the drawing takes the longest especially because I'm using an anti-aliasing module. (Oh, and I know PB has AA built in, just not in GDI basic 2D graphics mode.)