To Nest or Not to Nest Else

[SMcNeill]

Actually, this exclusionary thinking may be quite useful to consider.   Think of this scenario:

A 20 pointed star spaceship is battling aliens in a space invaders style game.  Pew! Pew!  Bullets and aliens everywhere!

Checking every possible point of impact with those 20 star points is going to be processing heavy...

So why not create an EXCLUSION check first?  If the object isn't within this simple circle distance of the center of my Starship, then skip it.

Now, you're not checking everything against every point of the ship.  You're only checking things that are outside that exclusion zone.

That should run and process a TON smoother!

---

That second method caused my brain to get stuck in an infinite loop ... or it possibly divided by 0, I can't tell which, LOL

That's almost exactly what my brain did!   After thinking about it a bit, it makes sense though.  It's just not intuitive to me.

If x < 300 Then 'it's left of the box
ElseIf x > 400 Then 'it's right of the box 
Elseif y < 100 Then 'it's above the box
ElseIf y > 200 Then 'it's below the box
Else 'it's not left nor right, nor above nor below the box... it has to be IN the box!


It works, and I might use it for some code obfuscation challenge, but it hurts my brain to think backwards like that.

The only issue I have with the code is that the IF and all ELSEIF statements must be processed. The method I've always used allows for dropping out of the statements when any of them go FALSE.

Imagine feeding this kind of backwards code thinking to LLMs. Let what appears to be hallucinations along with real hallucinations begin!

Nope.  Think about it a little deeper.

IF x < 300 THEN
   'Do nothing, but we could if we wanted too...
ELSEIF x > 400 THEN  <-- we'll skip this and all other ELSEIF and ELSE statements, if the first condition was true.