Day 026: ERASE

[mnrvovrfc]

Run it, open Task Manager...  Your program will use about 50MB of memory.   Hit any key, you go into SUB foo, and now are using over 1GB of memory.  Hit any key, exit foo, and that memory is now freed.  You're now back down to using the same 50MB of memory as previously.

No memory leak here.

So it means "CLEAR" is worthless in QB64 for its third parameter?

Maybe a redundant question since we're not in 16-bit any longer but declaring a static array that huge would have meant outright refusal to compile in the past. That's why I was being naive and said the thing about "memory leak".