Currently almost every element does start with an uppercase letter in AHK's document, which may result in many people as well as V2 edit extensions imitating the unintentional 'style' from the document.
A maybe proper suggestion:
Start with a lowercase letter for obj's property names like obj.base and keywords like if,return.etc.
Still start with an uppercase letter for class names, function names and method names.
[Suggestion:]Naming conventions in AHK document
[Suggestion:]Naming conventions in AHK document
Last edited by V2User on 15 Aug 2023, 08:42, edited 4 times in total.
Re: [Suggestion:]Naming conventions in AHK document
Hi,
that's a matter of personal taste. I prefer the 'uppercase style'.
that's a matter of personal taste. I prefer the 'uppercase style'.
- emmanuel d
- Posts: 97
- Joined: 17 Nov 2013, 04:45
Re: [Suggestion:]Naming conventions in AHK document
Naming like:
That is like pretending commands stil exist. it should have bin removed from the getgo.
Now it is unclear what is a function an what isn't. Just because it returns no value is no reason to write it like a command.
when converting to v2 we have to convert most of the parameters anyway
use:
also, note the [ is in the wrong parameter, only in a few cases in the manual is it in the wright place.
that requires extra clicking and selecting on copy paste, realy not efficient
so preferably:
Code: Select all
FileMove SourcePattern, DestPattern [, Overwrite]
Now it is unclear what is a function an what isn't. Just because it returns no value is no reason to write it like a command.
when converting to v2 we have to convert most of the parameters anyway
use:
Code: Select all
FileMove(SourcePattern, DestPattern [, Overwrite])
ComObjQuery(ComObj, [SID,] IID)
that requires extra clicking and selecting on copy paste, realy not efficient
so preferably:
Code: Select all
FileMove(SourcePattern, DestPattern, [Overwrite])
Return to “Suggestions on Documentation Improvements”
Who is online
Users browsing this forum: No registered users and 7 guests