suggestion: change to _MEMFREE
#2
Lightbulb 
Good idea! "ERASE" supports multiple array variables. But it would have to be done with "_FREEFONT", "_FREEIMAGE" and "_SNDCLOSE" as well.

But don't "_MEM" blocks have to be freed in a specific order, to prevent memory leak? The static UDT variable (ie. what is needed before "_MEM" function, "_MEMNEW" etc. is used) would take up space anyway so it shouldn't matter.
Reply


Messages In This Thread
suggestion: change to _MEMFREE - by OldMoses - 12-11-2022, 12:43 PM
RE: suggestion: change to _MEMFREE - by mnrvovrfc - 12-11-2022, 01:03 PM
RE: suggestion: change to _MEMFREE - by OldMoses - 12-11-2022, 01:32 PM
RE: suggestion: change to _MEMFREE - by SMcNeill - 12-11-2022, 01:57 PM
RE: suggestion: change to _MEMFREE - by Pete - 12-11-2022, 05:52 PM
RE: suggestion: change to _MEMFREE - by OldMoses - 12-11-2022, 07:54 PM



Users browsing this thread: 3 Guest(s)