AutoIt Cheat Sheet
Go to solution Solved by SOLVE-SMART,
Recently Browsing 0 members
No registered users viewing this page.
Okay it's about the style of the AutoIT Language. Concerning:
BitAND, BitOR, BitXOR, BitXOR,
That's a very simple but fundamental question:
Why BitAND is not infix?
In most other common programming languages it is.
Result = Value & Mask
But on AutoIT it's
$Result = BitAND ( $Value , $Mask ) That's more the Lisp / prefix way.
While the logical and is indeed infix
$bIsEnable = $bIsGUI_chkEnabled and $bIsGUI_chkChecked
So I wonder why it is like this.
What is the Idea behind this language design decision?
Okay Autoit is a matured Language but yeah - It's never to late for a change.
Wasn't there ideas to unify it any way?
So we also make the 'Bit' operations infix as well?
... while Just keeping the 'old' prefix version -for backwards compatibility - as well.
UPDATE #1: Now I created a ticket for this:
Well to generalise/modulate It more I may bring it down to the Subject Verb Object thing you have with language.
"I go swimming" that's S-V-O or some infix.
"Swimming I go". is O-S-V - postfix and sound much like yoda-style. While
"go I swimming" is V-S-O - prefix and 'feels' more like kinda question.
There is no right or wrong here - however personally I find infix is most appropriate here.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!Register a new account
Already have an account? Sign in here.Sign In Now