Custom Query (3910 matches)

OnAutoItExitRegister() set functions get stripped in Obfuscated result. (1.0.26.13|1.0.26.18)

#Region ;**** Directives created by AutoIt3Wrapper_GUI ****
#AutoIt3Wrapper_Version=Beta
#AutoIt3Wrapper_Run_Obfuscator=y
#Obfuscator_Parameters=/striponly
#EndRegion ;**** Directives created by AutoIt3Wrapper_GUI ****
OnAutoItExitRegister("MyTestFunc")
Func MyTestFunc()
	Return
EndFunc
;~ Exit ; workaround.
;~ MyTestFunc() ; workaround.

The wording used in the helpfile, Datatypes section (when a string is "used" as a number) pushed me to try some tests whose results go against the common explanation repeatedly given: "if a number is compared to a string, the later is evaluated as Number(string)". In short, we have that:

(5 = Number("5abc")) returns True, but (5 = "5abc") returns False !?! ("5abc" = 5) returns False !?! (just checking) (0 > "5abc") returns False !?! (1 > "5abc") returns True !?! (5 > "5abc") returns True !?!

It _sounds_ like the current rules are something along those lines:

any string containing one or more non-(digit or minus) is evaluated as integer 0

Reals have other rules:

(5 = 5. ) returns True (5 = '5.') returns False (5. = '5.') returns False

Perhaps the behavior of comparison between strings and numerics should be clarified. Or Number() should convert the string before comparison, which could possibly break existing (doubtful) code.

I still don't know if this ticket really is a feature request, a documentation clarification request or a bug report.

I have noted that when the port is closed from remote side , TCPrecv returns "" and set @error to -1.

1/ TCPlocal successfull on local side 2/ TCPrecv sucessfull on local side 3/ remote host close it's port.(tcpclose) 4/ further local TCPrecv returns "" and @error is set to -1

Documentation just says : Returns "" and set @error according to Windows API WSAGetError return.

It should be great to get an explanation in documentation about -1 return code (-1 is NOT a windows socket error code)

Thank's