-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
follow one naming standard when naming variables #293
Comments
OK, I take that comment back, seems it will compile either way. Seems the convention is to use all capitals (a github search |
please follow one style on all similar files. if the tool you rely upon insists in converting everything to all-capitals, I guess we have to adapt. if it does not, we have a choice. if we do have a choice, you must anyway either |
closing dangling issues |
Expected behaviour
single or at least consistent naming style
Actual behaviour
many variables in the new
scripts/build-multiuser.nsi
are all UPPERCASE (not all of them), a new file in thescripts
directory starts with uppercase.this produces an inconsistent structure, where the reader may be confused and wonder if the difference is significant. if it is not, please change back to all lowercase.
this snippet shows the situation:
it looks confusing, some definitions are "SHOUTING", some are quiet.
same for
Add_to_PATH.vbs
: it's the only file in the whole directory starting with a capital letter. traditionally, first upper case letter was meant to pull a file to the top of the listing. now less relevant, but still better follow a single naming style.it's not a bug, really, though it may bug readers.
The text was updated successfully, but these errors were encountered: