You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Function arguments have multiple coding standard. One of them is prefixing all function arguments with i or o. This is a naming convention I learned at work and I do not think it is largely used in the outside world. The goal is to prefix variables with an i when the variable is an input and an o when the variable is an output (like Parse() functions defined in RapidAssist).
I consider removing the i and the o prefixes as I don't think it is intuitive enough for people outside of my work environment. I am also not always consistent across all files.
end2endzone
changed the title
Uniformalize function argument names. Remove i and o from argument names
Uniformalize function argument names. Remove i and o prefix from argument names
Apr 26, 2021
* feature-issue47:
* Fixed issue #47: Allow generating into subfolder. * Fixed issue #50: Change File and FileManager macro guards prefix according to specified namespace.
Moved code related to directory parsing to a dedicated function `processInputDirectory()` to match `processInputFile()` function behavior.
Additional changes for issue #39: Uniformalize function argument names. Remove i and o prefix from argument names.
Small code simplifications for clarity.
Renamed some function arguments. Implemented IGenerator::setHeaderFilename() and IGenerator::getHeaderFilename()
Function arguments have multiple coding standard. One of them is prefixing all function arguments with
i
oro
. This is a naming convention I learned at work and I do not think it is largely used in the outside world. The goal is to prefix variables with ani
when the variable is an input and ano
when the variable is an output (like Parse() functions defined in RapidAssist).I consider removing the
i
and theo
prefixes as I don't think it is intuitive enough for people outside of my work environment. I am also not always consistent across all files.We might also adopt function arguments naming convention defined in Google's C++ Style Guide.
The text was updated successfully, but these errors were encountered: