Custom Query

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (70 - 72 of 3827)

Ticket Resolution Summary Owner Reporter
#876 Rejected @error passthrough on 'Return' statements Ascendant
Description

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)

#2038 No Bug For Windows 7 Java UDF is not working properly AshishJ
Description

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.

#3570 Duplicate Array index statements are called twice when used in a assignment AspirinJunkie
Description

When values assigned to an array element, the index statement seems to be evaluated twice. If only the array value is used in another statement this behavior does not seem to be occurring.

Example:

Global $aArr[12]

$aArr[MsgBox(0, "", "appear twice")] = "Test"

$x = $aArr[MsgBox(0, "", "appear once")]

AutoIt v.3.3.8.1 and below haven't got this problem. With 3.3.10.2 (x86 and x64) and greater i can reproduce this behaviour. Versions between 3.3.8.1 and 3.3.10.2 were not tested.

Note: See TracQuery for help on using queries.