Search the Community

Hi folks 👋 , I was thinking about how I decide to learn a new programming language. I mean, apart of professional requirements, there are some criteria for how I (and also some of my colleagues) choose a new technology or programming language. To get a good overview about how the language is written, how the syntax looks like and fits this my interests and expectations, I use cheat sheets for the specific programming language, a technology or methodology. Also for experienced programmers who want to switch a language or as an addition, it could be helpful to understand some basics, syntax etc. Is there any cheat sheet for AutoIt? I didn't find any. Do we need it as a community or at least would it be helpful? Would there be some of you supporting the idea of creating one? Do some of you know about templates that could be used (out of the box)? In case you are not familiar with the topic¹ and you do not know what I am talking about, please simple do a google search for "cheat sheet programming languages". 💡 There are hundreds of them, but non of these are for the AutoIt language². To spread this wonderful language to more people in the world, to support the accessibility, it should be a "must have" (among other things). I plan to build one => in best case as a community project with several of yours. Who wants to join? Best regards Sven ¹ A cheat sheet is a quick look-up reference chart or set of simple, brief instructions for accomplishing a specific task. ² It does not matter whether it's a PDF or a image in the forum which is well linked and present (next to the help) or a website. 📅 Update 2023-02-21: AutoIt (en) Cheat Sheet 🔗 AutoIt (en) Cheat Sheet as website on cheatography (a website which is made to create and publish cheat sheets by the help of templates) 🔗 AutoIt (en) Cheat Sheet as PDF (generated by cheatography) 🔗 Alternative Link to the PDF

Okay it's about the style of the AutoIT Language. Concerning: BitAND, BitOR, BitXOR, BitXOR, BitShift, BitRotate That's a very simple but fundamental question: Why BitAND is not infix? In most other common programming languages it is. Let's take JavaScript. Here I write: 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: https://autoitscript.com/trac/autoit/ticket/3752 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.