Quote:
Originally Posted by [Beatrice]
Well since i really got accustomed to the syntax i wonder how your custom syntax is atm. Would you mind writing an example code that shows basic function, variable declaring and some if/else and some other basic functions? Thanks a lot Looking forward to see your project! Keep it up!
|
There are no functions implemented yet. So you can "just" do the basic things like array-manipulation, function-calling, variabled-declaration, if/while/etc.
I also think there wont be that much function available in alpha version. Just the very basic functions to test if and especially what is working/not working.
But I am planning to implement all functions (maybe with different syntax/names) that are available in AutoIt.
But I do not want to develop this language because we need to "automate windows faster" (because usually you dont need to speed click on a button).
My main intention for this language is game manipulating/botting/hacking.
So my first focus will be on functions which helps you developing hacks and bots. I am thinking about things like Dll-Injection (and also the possibility to create some Dlls with this language), Hooking, Reading/Writing Memory, injecting assembler without any extern libaries and so on.
So the main syntax isnt that different from AutoIts one. It is just more consistency.
This means the following AutoIt-Code:
PHP Code:
Dim $var[1000][10]
$i=0
$i3=0
for $i=0 To 1000
if $i>2 Then
while $i3<10
$var[$i][$i3] = 999
$i3+=2
wend
EndIf
Next
Would look like that now:
PHP Code:
Dim $var[1000][10]
$i=0
$i3=0
for $i=0 To 1000
if $i>2
while $i3<10
$var[$i][$i3] = 999
$i3+=2
EndWhile
EndIf
EndFor
Especially the "then" after if annoyed me many many times. So I removed it.
It is useless as hell and I cant think about any situation where you need a then in multiline-ifs.
If you use a one-line if the then must be place to make clear what belongs to comparision and what not.
Also I changed things like "WEnd" and "Next" to "EndWhile" and "EndFor".
I always aked myself why the hell we need a "next" if we use a "for"-loop.
At the very beginning I always tended to use "EndFor" as you normally do in AutoIt.
Like "Select" and "EndSelect", "Switch" and "EndSwitch", "Func" and "EndFunc", etc.
So in my opinion not using EndWhile and EndFor makes it unnecesserary harder to get started.
So I removed/changed that.
There will be the same for future keywords like "Class" and "EndClass". I want to have got a high concistency.
Also things I always struggled with were something like that:
PHP Code:
Dim $var[5]
for $i=0 to 4
$var[$i] = _StringBetween(...)
next
Why isnt this possible but this works like a Charm:
PHP Code:
$var = _StringBetween(...)
I really think there are many things that can be done much better. Not just regarding to speed but also to Syntax and Semantic.
While developing the Compiler/Interpreter, I really understood how fast AutoIt is.
The parsing/interpreting/executing is unbelievable fast.
There are still some very rare situations where my interpreter is just a few ms faster than the corresponding AutoIt-Code.
So to sum it up:
Hell yeah thats a hard competitor but Im sure we (I gonna release it as open source so everyone can help me) can do it better if we are all helping together. :)
Edit:
I also added things like "bit operators", because I guess its very handy to just write a "<<" instead of a "BitShift(...)".