Latest Beta

[Kip]

Now we have function pointers, we're one step closer to inline function declarations.

$myCallback = Func($x)
     MsgBox(0, "", $x)
EndFunc
$myCallback(8)

[Valik]

We have already discussed unreachable functions. The code should throw an error message but she may not have that error message implemented yet. This should not be possible:

Func MyUDF()
EndFunc

Global MyUDF = "anything"   ; Syntax error

That is supposed to generate an error with a message along the lines, "Unable to reassign function". This will be possible only due to scoping rules:

Func MyUDF()
    ConsoleWrite("MyUDF()" & @CRLF)
EndFunc

Func AnotherUDF()
    Local MyUDF = MyUDF
    MyUDF()
    MyUDF = ""
    ; Can no longer call MyUDF() from this scope
EndFunc

AnotherUDF()
MyUDF()

[czardas]

It's looking very promising.

Edited April 17, 2012 by czardas

[Shaggi]

Indeed, that's some very additions. Good job

[JohnOne]

Is scite playing nice alongside this alpha version? (I wouldn't even know how to use it)

I would imagine obfuscator might not befriend the newer optional syntax so gracefully.

[Valik]

I've just uploaded a new alpha version. I also uploaded the current documentation source.

3.3.9.5 complete changelog:

AutoIt:

- Added: Empty arrays.

- Added: Functions are now first class objects which means variables can "point" to them and the function can be called through the variable.

- Added: The $ prefix for variables is now optional and can be omitted entirely.

- Added: Built-in functions that take a callback now be passed directly in addition to the old method of passing as a string. Built-in functions can also be passed now (be careful that the function you pass matches what the caller expects).

- Added: C++ style ternary operators: Local bResult = ("foo" = "bar") ? True : False

- Fixed: Redim allows initialization to non-array.

- Fixed #2166: StringToASCIIArray() and StringFromASCIIArray() did not correctly return an empty string when the start index is greater than the end index.

- Fixed #1901: 32-bit compiled scripts now work from the system32 directory on 64-bit Windows.

- Changed: Optional square brackets for array declaration with initialization.

Au3Check:

- Changed: Optional square brackets for array declaration with initialization.

There are a couple things I forgot to document on trancexx's behalf. There should now be an error when you attempt to re-assign a function name (the error message will change):

Func MyUDF()
EndFunc

Global MyUDF = "anything"

There's also a new feature that is not ready for use and thus is not documented. Some of the MVPs may have noticed it get added but it should not be used until you see it in the documentation. It is subject to change so keep that in mind if you stumble across it.

[matwachich]

Just a small question:

Does these modifications have any impact on performances???

Thanks

[Valik]

Just a small answer:

I don't care.

It's an alpha. Features have to start somewhere. If you want fast stable code then don't use alpha/beta software.

Edited April 23, 2012 by Valik

[Kip]

You know what would be really awesome?

If function pointers could be passed with COM methods. (Instead of creating a VT_EMPTY variant like it does now)

[MvGulik]

Number() (3.3.8.1)(3.3.9.4)

Not sure if this is something that already passed by somewhere else (a long time ago) ... but

Number(Bool, or 'Default') = Double(type) ... Double type output, instead of int(32/64), being intentional?

[trancexx]

Number() (3.3.8.1)(3.3.9.4)

Not sure if this is something that already passed by somewhere else (a long time ago) ... but

Number(Bool, or 'Default') = Double(type) ... Double type output, instead of int(32/64), being intentional?

I'd spank you if I could now.

Use normal fucking language.

[MvGulik]

... I could if I would ...

So is that a bonded 'Yes', or a tight up 'No'.

[trancexx]

First one.

[twitchyliquid64]

Just a quick question:

How does this new version of AutoIT distinguish between variables and other words/identifiers now that the '$' is optional? does it just look it up in a table of keywords?

[ProgAndy]

Just a quick question:

How does this new version of AutoIT distinguish between variables and other words/identifiers now that the '$' is optional? does it just look it up in a table of keywords?

AutoIt searches in its tables for the name. The order should be this:

Assigning a variable: keywords (error if name exists), functions (error if name exists), variables

Using a variable/keyword: keywords, variables, functions

Calling a function: variables (error if found, but no function reference), functions

Edited April 23, 2012 by ProgAndy

[Valik]

Why do you care how it does it as long as it works?

[jchd]

What's the rationale for making VarGetType(1 = 1) etc. a Real and not Int?

It has unexpected consequences (well, in pathalogical uses the help file warns against):

ConsoleWrite(VarGetType(0 + (1=1)) & @LF)
ConsoleWrite(100000000000000 + (1=1) & @LF)
ConsoleWrite(1000000000000000 + (1=1) & @LF)
ConsoleWrite((10000000000000000 = 10000000000000000 + (1=1)) & @LF)

[Valik]

An incomplete feature that you just reminded me about.

[twitchyliquid64]

Why do you care how it does it as long as it works?

I am building systems that mirror the behaviour of the Autoit interpreter. It is easier for me to implement new behaviour if I have some little idea of what goes on under the bonnet.

[Valik]

Trust me on this: You're wasting your time. Maybe come back and try again in a year. Right now, though? Not such a good time to try that.