ConsoleWrite do not preserve @error

[Zvend]

The helpfile for ConsoleWrite says

---

"The @error and @extended are not set on return leaving them as they were before calling. Usefull when debugging with the SciTE debugging output."

---

Sadly it is not true...

Test()
ConsoleWrite(@error & @CRLF)



Func Test()
    SetError(1, 0)

    ConsoleWrite("Test" & @CRLF)

    Return
EndFunc

[Jos]

It looks like when a ConsoleWrite is used in the Func, the @error is not kept in the return information. These 2 versions work fine, where as the OP's script indeed doesn't work:

Test1()
ConsoleWrite("Test1 master:" & @error & @CRLF)
Func Test1()
	SetError(1)
	Return
EndFunc   ;==>Test1

Test2()
ConsoleWrite("Test2 master:" & @error & @CRLF)
Func Test2()
	SetError(1)
	ConsoleWrite("Test2 func:" & @error & @CRLF)
	Return SetError(@error)
EndFunc   ;==>Test2

[anonymous]

This ticket appears to be wrong... ConsoleWrite does work as documented in 3.3.16.1 !
Here's a wee better snippet demonstrating the behavior, comments say it all:

Test1()
ConsoleWrite("Test1 1: " & @error & @CRLF) ; 1234,  as expected, 
;in versions 3.15.0/1/2/3/4, 3.16.0/1

ConsoleWrite("Test1 2: " & @error & @CRLF) ; 1234  ONLY in 3.15.4 
; and 3.16.1; notably, 0(zero)  in 3.16.0!

Func Test1()
        SetError(1234)
        Return
EndFunc   ;==>Test1

Test2()
ConsoleWrite("Test2 1: " & @error & @CRLF) ; 1234 in 3.15.4 and 3.16.1, zero in other versions.
ConsoleWrite("Test2 2: " & @error & @CRLF) ; 1234 in 3.15.4 and 3.16.1, zero in other versions.
Func Test2()
        SetError(1234)
        ConsoleWrite("Test2 func 1: " & @error & @CRLF) ; 1234,  as expected, in 3.15.0 - 3.16.1
        ConsoleWrite("Test2 func 2: " & @error & @CRLF) ; 1234 in 3.15.4 and 3.16.1, zero in other versions.
        Return ; note the absence of SetError(@error); it's unnecessary for versions 3.15.4 and 3.16.1
        ; in other versions ConsoleWrite simply does NOT preserve @error, so SetError(@error) here would be useless.
EndFunc   ;==>Test2

[anonymous]

also, the title is... inadequate! this ticket has nothing to do with SetError! SetError does, and always did, work as expected/documented.

[Jpm]

Fix sent to Jon