Thread: Static Local Variable vs. Global Variable

If I were to give you a simple response, I would then have to kill you. Just kidding. Well, short answer is, it depends. Long answer is, you could be doing craziness such as writing to memory that is not in the stack or even altering memory that is not accessable by your program. This is a classic example of "just because it compiles doesn't mean it should even work." For large pools of memory it is typically better to use malloc() (or whatever...) anyway. Plus, using static locals isn't necessarily the most thread safe way to go about life.

Problem solved. Turns out I'm a doofus and you guys should be laughing and pointing fingers at me.

I adapted my function from a Seed-Fill algorithm published by a guy named Paul Heckbert in the 80's. Unfortunately, I didn't pay attention to the fact that his upper bounds were INCLUSIVE, and I needed exclusive bounds.

I was trying to access pixels one past the end of the array in both the X and Y directions. For smaller 2D arrays this wasn't a big deal, but for a large array I was treading WAY out of bounds if I went one row too far, and that was causing the crash.

Forgive my lameness, even though it is extreme.

Be kind to yourself. Otherwise we are all doofus sometimes. More times than any of us would outrightedly admit to.