- I have been programming to some extent for approximately 20 years. AutoHotkey from around 2010 onwards, I had a quite wide knowledge of Excel macros before that. I did experiment with serious languages before trying AutoHotkey, and have done some C++.
- Re. the AutoHotkey syntax, I don't think that many people could know it much 'better' than I do, especially since I've written converters/parsers/correctors that handle every nuance of the language. People may know behind-the-scenes details re. syntax better than me, and I haven't needed to use AHK object classes much.
- Re. 'a little hard thinking', I usually make proposals based on custom functions that I have tested for months or years, the testing often reveals a beneficial slight tweak. A lot of thought goes into for example: function/parameter naming/order, generality (being able to use a function for a wide variety of purposes), consistency with existing functions.
- I often see overlap with some of my ideas in other forum threads, unfortunately, other people don't often comprehensively collect their ideas, so it's harder to compare notes.
- Btw I do go over things quite thoroughly, some weeks ago, I reread 'Changes from v1.1 to v2.0' in full, which took about 2 hours, and I recently read the 3 new pages in the documentation (Program/Concepts/Language). You claim that other users consider things carefully too, but for example, I don't often see people take on problems in a comprehensive way, like with my list of built-in functions/variables, documentation extension, GUI control zoo, ranking of AHK v2 conversion difficulties, list of best scripts, or RegEx tutorial, and I don't see too many tutorials (where the consideration of all possible readers is a major challenge). One exception is HotKeyIt's WinApi link which I am very grateful for.
- Suggestions relating to making scripts two-way compatible have been more challenging. I've only become well-versed in AHK v2 this year, and, the nature of AHK v2 has been changing. Principles like 'pseudo-arrays are always bad' and 'don't change AHK v2, only change AHK v1', have made me rethink various approaches to fit in with those demands.
- I recently discovered this thread:
AutoHotkey v2 Alpha Release - Scripts and Functions - AutoHotkey Community
https://autohotkey.com/board/topic/6531 ... a-release/
Trying to take on board all of these proposals really expands your horizons as someone who wants to design functions and possibly propose syntax additions.
- The 'AHK v2 is a subset of AHK v1' (syntax-wise) point was actually more like one of your points, rightly or wrongly I assumed the reader could figure it out, I avoided stating all the minor details (, and I was brief because it was responding to something offtopic). When I converted my scripts to AHK v2, the number of syntax concepts decreased: no "" (` became the only escape character), no commands, no 'force expression', no 'can be an expression', no ClipboardAll special variable, fewer variables that don't start with 'A_' (ComSpec, ProgramFiles, %0%, %1%), between/in/contains removed, simpler GUI handling (no g-labels), fewer characters requiring escaping (in expression-style parameters), one type of continuation section, binary variables can be used like normal variables, +=/-= for dates removed, #NoEnv by default, no AutoTrim.
- Anyway, I had the intention of finishing all my code projects, functions, tutorials, and submitting my AHK v2 proposals within a year of being the forum which I've mostly done. Although tidying and submitting my backlog of scripts could take at least 3 years.