AutoIt v3.3.13.16 Beta

[Jon]

File Name: AutoIt v3.3.13.16 Beta

File Submitter: Jon

File Submitted: 07 Aug 2014

File Category: Beta

3.3.13.16 (7th August, 2014) (Beta)
AutoIt:
- Added: Regular expression caching. Small performance improvements when using the same pattern multiple times.

- Fixed: Assigning objects by reference to COM properties like "$obj(some, params) = $obj2".
- Fixed: Regression with Redim.

UDFs:
- Added #2826: Quit to close the browser.

- Fixed #2828: Typo of security in _IEFormElementSetValue().

Others:
- Fixed: Re-writing the scripts which generate the syntax files for the editors and GeSHi, resulted in missing descriptions being added and correct sorting of functions.

Click here to download this file

[mLipok]

using example form MapKeys

I have this results:

Key: 1
Value: Integer One
Variable Type: Int32

Key: 2
Value: String Two
Variable Type: String

Key: 2
Value: Integer Two
Variable Type: Int32

Why the third key is not Key: 3 instead Key: 2   ?

[mLipok]

Where to post proposals for HelpFile Example to the Map functions ?

[guinness]

using example form MapKeys

I have this results:

Key: 1
Value: Integer One
Variable Type: Int32

Key: 2
Value: String Two
Variable Type: String

Key: 2
Value: Integer Two
Variable Type: Int32

Why the third key is not Key: 3 instead Key: 2   ?

Because MapAppend() uses the next largest integer value, which is 2 as the 2 added previously was a string. This is the sole reason we added this example plus the comments kind of explain.

Where to post proposals for HelpFile Example to the Map functions ?

Here for now.

Edited August 7, 2014 by guinness

[mLipok]

so here is example proposal (modyfication) for MapRemove

expandcollapse popup

#include  <MsgBoxConstants.au3>

Example()

Func Example()
    ; Declare a map and assign with various keys value pairs.
    Local $mMap[]
    Local $sTempKeyName = "Jasper"

    $mMap[$sTempKeyName] = "Jasper value"
    $mMap[1] = "One value"
    $mMap["Beethoven"] = "Beethoven value"
    $mMap["Pinky"] = "Pinky value"
    MapAppend($mMap, "Append 'Key#2' value")

    ; Read keys
    Local $sData
    $sData = MyMapToString($mMap)

    ; Display result
    MsgBox($MB_SYSTEMMODAL, "Test 1", $sData & @CRLF & _
            "Beethoven exists: " & MapExists($mMap, "Beethoven") & @CRLF & "Beethoven equals Null: " & ($mMap["Beethoven"] == Null))

    ; Clear a key by setting it to Null. The key will still exist in the map.
    $mMap["Beethoven"] = Null

    ; Re-read keys and values
    $sData = MyMapToString($mMap)

    ; Display the values of the map keys. Notice how the "Beethoven" key now contains an empty value (Null).
    MsgBox($MB_SYSTEMMODAL, "Test 2", $sData & @CRLF & _
            "Beethoven exists: " & MapExists($mMap, "Beethoven") & @CRLF & "Beethoven equals Null: " & ($mMap["Beethoven"] == Null))

    ; Remove the "Beethoven" key entirely.
    MapRemove($mMap, "Beethoven")

    ; Re-read keys and values
    $sData = MyMapToString($mMap)

    ; Display the values of the map keys. Notice how the "Beethoven" key is no longer exists.
    MsgBox($MB_SYSTEMMODAL, "Test 3", $sData & @CRLF & _
            "Beethoven exists: " & MapExists($mMap, "Beethoven") & @CRLF & "Beethoven equals Null: " & ($mMap["Beethoven"] == Null))

EndFunc   ;==>Example

Func MyMapToString($mMap)
    Local $aKeys = MapKeys($mMap)
    Local $sData = ""

    ; Read values
    For $i = 0 To UBound($aKeys) - 1
        $sData &= $aKeys[$i] & ": " & $mMap[$aKeys[$i]] & @CRLF
    Next

    Return $sData
EndFunc

[guinness]

Thanks. I will leave as is just for the second, since the map data structure is still being tested.

[eukalyptus]

I did some speed tests on Map and Scripting.Dictionary.

Map is superfast - yeah!

 

And I think, I've discovered a bug:

Global $oDic = ObjCreate('Scripting.Dictionary')
$oDic.Add(1, 1)
$oDic.Add(1, 1)

gives this output:

"D:AutoItBetaTestTest_Dict.au3" (3) : ==> Unknown function name.:
$oDic.Add(1, 1)
$oDic^ ERROR

[Melba23]

Jon,

The new Beta is breaking IE.au3 big-time:

#include <IE.au3>

$oIE = _IEAttach("http://www.autoitscript.com/forum/", "URL")

3.3.12.0 does not crash on this code - I have not yet checked any previous Betas.

M23

Edit:

(344) : ==> Unknown function name.:

Edited August 9, 2014 by Melba23

[guinness]

; Isolated.
Local $oShell = ObjCreate("Shell.Application")
Local $oShellWindows = $oShell.Windows(), $iIndex = 0
ConsoleWrite($oShellWindows.Count & @CRLF)
For $oExplorer In $oShellWindows ; http://msdn.microsoft.com/en-us/library/windows/desktop/aa752084(v=vs.85).aspx#methods
    ConsoleWrite($iIndex & ' >>' & $oExplorer.AddressBar & @CRLF) ; True or False.
    ConsoleWrite($iIndex & ' >>' & $oExplorer.FullName & @CRLF)
    ConsoleWrite($iIndex & ' >>' & $oExplorer.LocationName & @CRLF)
    ConsoleWrite($iIndex & ' >>' & VarGetType($oExplorer.Type) & @CRLF)
    ConsoleWrite($iIndex & ' >>' & $oExplorer.Type & @CRLF)
    ConsoleWrite(@CRLF & @CRLF)
    $iIndex += 1
Next

[Jon]

.Type seems to only exist for IEXPLORER.EXE certain iterations of that loop and not EXPLORER.EXE.  It was actually calling the COM error handler on the old version and new version. But in the old version it was also silently failing for invalid properties which the rewrite addressed ($var = $oObject.invalidproperty didn't actually fail...).  

Not quite sure what/how this should be fixed. I could do with the same code in VBS to see what happens there.

Global $iEventError = 0 ; to be checked to know if com error occurs. Must be reset after handling.

$oMyError = ObjEvent("AutoIt.Error", "ErrFunc") ; Install a custom error handler

; Isolated.
Local $oShell = ObjCreate("Shell.Application")
Local $oShellWindows = $oShell.Windows(), $iIndex = 0
;ConsoleWrite($oShellWindows.Count & @CRLF)
For $oExplorer In $oShellWindows ; http://msdn.microsoft.com/en-us/library/windows/desktop/aa752084(v=vs.85).aspx#methods
    MsgBox(0, "", $iIndex & ' >>' & $oExplorer.FullName & @CRLF)
    $var = $oExplorer.Type
    MsgBox(0, "", @error)
;    MsgBox(0, "", $iIndex & ' >>' & $oExplorer.Type & @CRLF)
;    MsgBox(0, "", @CRLF & @CRLF)
    $iIndex += 1
Next

; This is a custom error handler
Func ErrFunc()
    $sHexNumber = Hex($oMyError.number, 8)
    MsgBox(0, "", "We intercepted a COM Error !" & @CRLF & _
            "Number is: " & $sHexNumber & @CRLF & _
            "WinDescription is: " & $oMyError.windescription)
    $iEventError = 1 ; Use to check when a COM Error occurs
EndFunc   ;==>ErrFunc

[Jon]

Similar bomb-out in VBS

set oShell = CreateObject("shell.application")

Set oShellWindows = oShell.Windows()

WScript.Echo oShellWindows.Count

For Each oExplorer in oShellWindows
    WScript.Echo oExplorer.FullName
    WScript.Echo oExplorer.Type
Next

[Jon]

Same with the scripting dictionary report.  Also bombs on VBS

set oDic = CreateObject("Scripting.Dictionary")
oDic.Add 1,1
oDic.Add 1,1

[guinness]

In the IE UDF the were a questionable comment of does it exist. I will contact Dale to amend his UDF.

[trancexx]

But in the old version it was also silently failing for invalid properties which the rewrite addressed ($var = $oObject.invalidproperty didn't actually fail...).

Wait, why should it fail? And how does it fail now? You mean like script terminates or what?

[KaFu]

Same with the scripting dictionary report.  Also bombs on VBS

set oDic = CreateObject("Scripting.Dictionary")
oDic.Add 1,1
oDic.Add 1,1

 

Because the method is not called correctly. .Add() does not check if the item exists, if it does, it errors out... interesting, also note that 1 and "1" are different keys.

$oDic = ObjCreate('Scripting.Dictionary')
$oDic.Add(1, 1)
$oDic.Add("1", "1")
; $oDic.Add("1", "1")
If Not $oDic.Exists("1") Then $oDic.Add("1", "1")
If Not $oDic.Exists("2") Then $oDic.Add("2", "1")
$oDic.Item("1") = "2"

For $oDic_Key In $oDic.Keys()
    ConsoleWrite($oDic_Key & @TAB & $oDic.Item($oDic_Key) & @CRLF)
Next

Edited August 10, 2014 by KaFu

[Jon]

Wait, why should it fail? And how does it fail now? You mean like script terminates or what?

Yeah, at the moment:

With error handler: runs handler

Without error handler: fatal error

This essentially mirrors what VBScript does with the same code. You have to wrap the erroring lines with "On Error Resume Next" to get it to work, which I guess is the closest equivalent of our error handler.

The COM code has been touched by so many people over the years that it's tricky to read what the intent was when reading a particular function. There are times when COM will give a fatal error if there is no handler, and other times it seems to be silently ignored - sometimes setting @error. I've tried to standardise it and comment it up whenever I've come across those situations.  I've isolated the changes I made where this particular scenario occurs but I guess it's as good a time as any to verify which approach we want to take.

[water]

 

... to verify which approach we want to take.

I would like to see @error always set when a COM error happens. If the user needs more information about the COM error he has to set up a COM error handler or use the _DebugCOMError function.

[jchd]

Same.

[water]

I have used this approach in my Word, Excel, Outlook and AD UDF and I'm quite happy with AutoIt not crashing any longer and just setting @error.

[Iczer]

About new addition - Regular expression caching - may i have small reproducer where this feature get max effect ?

as a side note - what about Regular expression compiling/precompiling?