[Trigger] A thing I can't figure out.

[lolreported]

Hmm, I fooled around with World Editor today and I thought: "What is fastest? A loop with actions or instant actions?

If you don't understand:

• First
  • Events
    • Unit - A unit Dies
  • Conditions
  • Actions
    • Set temp_point = (Position of (Triggering unit))
    • Unit - Create 1 (Unit-type of (Triggering unit)) for (Owner of (Triggering unit)) at temp_point facing Default building facing degrees
    • Custom script: call RemoveLocation(udg_temp_point)

^Thats a trigger without a loop.

• Second
  • Events
    • Unit - A unit Dies
  • Conditions
  • Actions
    • For each (Integer A) from 1 to 1, do (Actions)
      • Loop - Actions
        • Set temp_point = (Position of (Triggering unit))
        • Unit - Create 1 (Unit-type of (Triggering unit)) for (Owner of (Triggering unit)) at temp_point facing Default building facing degrees
        • Custom script: call RemoveLocation(udg_temp_point)

^Thats a trigger with a loop.

And now I want to know which trigger is the fastest? :S

 

[ady_illidan]

the first one. why to make a loop for such a simple trigger?

 

[lolreported]

Just a test. Anyway, my thought is that the trigger runs faster with a loop.

 

[emperor_d3st]

And just why the hell would it run faster with a loop?
It means it has more to process, more stuff to store.

 

[NoNZealot]

Like it has to make a loop, puts actions, and then close the loop and ALL the actions. However this is not on the first one. Just a simple action.

 

[PurplePoot]

The loop is always slower, but speed is not the only factor.

• Loops can go for variable lengths
• They greatly shorten code

 

[lolreported]

Yes, I knew that the first trigger is faster, but anyway, I has a feeling that if I put actions in a 1/1 loop, the actions would run alot faster ^^

 

[PurplePoot]

That makes no sense.