Why the command names are so difficult Topic is solved

[The fortunate One]

Actual conversation with my student

Student's question/statement
Student: Sir, Why is the "Pause" or Delay" is called "Sleep"
Student: The "designers"(of A H K) must be really "Stupid"

My answer
Me: That is a horrible thing to say
Me: Example, if the word "Pause" is used as a "command" then "we" cannot use "Pause" as "variable" without a "workaround"
Me: Also please don't under estimate the brilliance of our dear designers
Me: And the trial and tribulations they have been through - "For you"(the user)
Me: Example, "Sleep" is more readily understood by non-English speakers

Student's comeback
Student: So, you want us to be "dumb-downed" as "foreigners"

My comeback
Me: So, you agree "AHK" is easy!
Me: By the way, Albert Einstein was foreigners

- Thank you reading - love and peace -

[nnnik]

Many of the command names immediately from it's corresponding Win API function.
e.g. https://msdn.microsoft.com/en-us/librar ... s.85).aspx << Sleep
Also many names indicate a more complex context.
In advanced programming you will just copy these conventions to keep these indications.

[TAC109]

Tell your student:-

• He is free to write his own AHK 'pause' and 'delay' functions and use these in his scripts.
• Alternativly he could write his own interpretive language where he can choose the command/function names to suit his tastes.