Whereas the concept of class-like syntax is great, I believe the keyword "class" is misleading. A class-object in AHK is not a class, in the typical sense of the word when comparing to most other languages. I feel this could lead to confusion to developers who are used to classes in other languages, as well as noobies who are tying to understand classes by comparing to other languages. I feel Prototype-based programming is correct for AHK, but using the keyword "class" just adds an un-intuitive twist to the already steep learning curve of Prototype-based programming.
Also, I realize the documentation clearly states:
... but why mix the two concepts?An object is a prototype or base if another object derives from it ... For convenience and familiarity, the "class" keyword can be used to construct a base object.
Also, since Prototype is longer, simply Proto could be an option. Or maybe even just Base.