Custom Query (3931 matches)

During testing, this UDF sometimes puts a ',' at the beginning of a number which isn't correct. For example, the below results in -,123,456,789,012,345.67890:

#include <String.au3>
MsgBox(16,"_StringAddThousandsSep() faulty reult", _
	"Result of _StringAddThousandsSep('-123456789012345.67890'): "& _
	_StringAddThousandsSep('-123456789012345.67890'))

_DebugBugReportEnv() Result:

Environment = 3.3.0.0 under WIN_XP/Service Pack 3 X86

It would be nice to be able to use 'Return MyFunction()' to both return the values from that function *and* the @error/@extended codes. It looks ridiculous, and is probably wasteful to change the below code:

Func _ReturnErr()
    Return SetError(1,0,1)
EndFunc

Func _ReturnReturnErr()
    Return _ReturnErr()
EndFunc

_ReturnReturnErr()
If @error Then ConsoleWrite("Error returned correctly"&@CRLF)

to this code:

Func _ReturnErr()
    Return SetError(1,0,1)
EndFunc

Func _ReturnReturnErr()
    ; Wasteful temporary storage
    $tempVal=_ReturnErr()
    ; This looks ridiculous, setting @error to @error:
    If @error Then SetError(@error,@extended)
    Return $tempVal
EndFunc

_ReturnReturnErr()
If @error Then ConsoleWrite("Error returned correctly"&@CRLF)

I recognize that there is function 'localization', but I believe that 'Return FunctionName()' makes more sense to return the value AND the @error\@extended code information. It would save extra work and make more sense in the end.

Actually, even better - I recommend a new keyword - something like 'ReturnWithSubError', which will take the last @error + @extended codes returned by a called function and return them as the @error/@extended values.

This will prevent breaking old code, and make code clearer, easier, and more sensible. Code with SetError(@error) looks (and is) ridiculous, in my opinion. (Sorry, don't mean to offend)

Please note that, I am trying to use Java UDF for Windows 7 Enterprise Edition 32 bit

It seems that most of the functions are not working properly.

I have some scripts written which are working very fine under Windows-XP.

Now I have migrated from Windows XP to Windows 7, It Seems that the Scripts are not working as expected like Windows XP.