Lol. Is that the point in the code where it crashed??
Quote from: JKnightandKARR on Mar 23, 2025, 06:20 PMLol. Is that the point in the code where it crashed??
Could be. The example is more BASIC (pun intended) by demonstrating that, depending on when your conditional is executed, you could end up executing more code than you expect (that's overly simplifying it).
In the graphic, the Roadrunner example is he evaluates his conditional BEFORE executing commands. The coyote on the other hand executes THEN checks the conditional evaluation, which may have returned a FALSE (meaning it should NOT have run).
Quote from: granz on Mar 23, 2025, 06:53 PMQuote from: JKnightandKARR on Mar 23, 2025, 06:20 PMLol. Is that the point in the code where it crashed??
LOL - Good one.
I thought so.
Quote from: Chris Savage on Mar 23, 2025, 09:48 PMQuote from: JKnightandKARR on Mar 23, 2025, 06:20 PMLol. Is that the point in the code where it crashed??
Could be. The example is more BASIC (pun intended) by demonstrating that, depending on when your conditional is executed, you could end up executing more code than you expect (that's overly simplifying it).
In the graphic, the Roadrunner example is he evaluates his conditional BEFORE executing commands. The coyote on the other hand executes THEN checks the conditional evaluation, which may have returned a FALSE (meaning it should NOT have run).
I know, that's why I asked, since the coyote is going to end up crashing into the ground below. lol