I\'m pretty bad with naming things. The only name I can every generically come u
ID: 653064 • Letter: I
Question
I'm pretty bad with naming things.
The only name I can every generically come up with is 'helper'. Say, if I have a header file that contains helping functions for manipulating paths, I tend to put it inside my "helper" directory and call it "path-helper.hpp" or something like that.
Obviouslly, that's a bad naming convention. :)
I want to have a consistent naming scheme for my folder (and namespace) which I can use to always refer to my own headers and libraries, but I have trouble finding names that are easy to type or remember (like boost)... so I end up calling some of them "helper" or "stdext" or whatnot, which isn't a great idea.
How do you find names for your libraries that are easy to remember and easy to type, and which aren't too generic (like "helper" or "std" or "stdext" or the like)?
Any suggestions on how to go about doing this?
Explanation / Answer
Try to group helper functions thematically and include the theme in the library name. A library name like "helper" may by too generic, but a name like "PathHelper", "FileIOHelper" says pretty much about what functions one can expect in that lib (personally, I prefer "...Utilities", but that's just a matter of personal taste). For example, I have lib names like "MathUtilities", "StringUtilities" "ConfigUtilities", "DBUtilities" and so on.
Of course, for bigger libraries in our team we use names without any generic term at the end. And to be honest, we have also a library called "Common" for some functions and classes which don't group well under a specific topic name. But we try to keep that lib small.