Fixed: Assigning objects by reference to COM properties

[MrCreatoR <mrgeorge.sandler@…>]

The fix described in the title probably broke new feature added in 3.3.10.0:

Changed: Run-time errors on objects no longer fatal (execution of the script is not halted).

Here is an example that works in 3.3.10.x, but produces fatal error in 3.3.14.x:

$oDict = ObjCreate('Scripting.Dictionary')

$oDict.Add('test', 'ok')
ConsoleWrite($oDict.Item('test') & @CRLF)

$oDict.Remove('test')

;Purpesly remove again not existing item, which will produce fatal error in 3.3.14.x
;Uncomment condition to solve this issue
;If $oDict.Exists('test') Then
    $oDict.Remove('test')
;EndIf

[jchd18]

Unless I missed it, it seems that the changelog didn't explicitely mention when COM errors have been reverted to the old benavior: fatal error or user-supplied COM error handler instead of directing COM errors to @error.

[water]

That's correct COM error handling has been reverted as you described.