Change DllCallbackFree() to check handle validation or erase it

[MsCreatoR <mscreator@…>]

From the help file:

If handle is invalid, an AutoIt runtime error will be thrown, and the script will terminate!

First of all, i think none of built-in functions should not to hard crash the script.
But if it's really inevitably, those functions should (optional?) recieve handle ByRef, and change the $handle to 0 after it's releasing the CallBack. Something like this:

Func _DllCallbackFree(ByRef $Handle)
	If $Handle > 0 Then
		DllCallbackFree($Handle)
		$Handle = 0
		Return
	EndIf
	
	Return -1
EndFunc

Because for now there is a chance that our script can crash when it's not supose to (in the middle of some task).

Thanks.

[TicketCleanup]

Automatic ticket cleanup.

[Jon]

I don't understand.

[Valik]

Jon, from the sounds of it, this is the same thing you used to have in place when an invalid file handle was passed to FileClose(). Remember how it used to throw up an error and stop the script? Remember how I bitched about that?

Oh, and this crashes AutoIt. Stupid, yes, but I was trying to generate something simple to reproduce the bug and ended up with a hard-crash:

DllCallbackFree(32)

Incidentally, flagging this as a bug, not a feature request.

[Jon]

Oh I see. K, I've removed the message for this and DllClose() as well.

[Jon]

Fixed in version: 3.2.13.4