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 is not 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.
We might also adopt function arguments naming convention defined in Google's C++ Style Guide.
This issue is related to #39.
Function arguments have multiple coding standard. One of them is prefixing all function arguments with
ioro. This is a naming convention I learned at work and I do not think is not largely used in the outside world. The goal is to prefix variables with aniwhen the variable is an input and anowhen the variable is an output (like Parse() functions defined in RapidAssist).I consider removing the
iand theoprefixes 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.
This issue is related to #39.