_WIDTH(_LOADIMAGE()) Ok?

[SMcNeill]

I recently saw some code that did this:

ImageWidth = _WIDTH(_LOADIMAGE("Image.png", 32))

Will this leave the image's contents in RAM with no way of freeing it?

-or-

Will the image be discarded since the handle was not assigned to a variable?

It's a neat trick and one that I could happen to use on a current project but not if the image is orphaned in RAM.

How is one going to _FREEIMAGE that?  As you suspect, chances are that's an image lost in RAM forevermore.

The only reason I say "chances are", is because image handles start at -10 and go downwards from there, so it's always possible some odd coder wrote something like:

FOR i = -10 TO -1000 STEP -1
  _FREEIMAGE i
NEXT