sensible C++ coding convention - µOS naming standard

RE: sensible C++ coding convention - µOS naming standard

battlecoder — Mon, 02 Sep 2024 03:08:47 GMT

Naming conventions are definitely a fighting ground for a lot of people. I personally think that any naming convention you want to follow is fine, as long as the code doesn't look like you put the ascii table in a blender and dumped it into your C file with some ice.

However, there's some extremist views out there, and I've seen coding style suggestions that are meant to "improve readability" in theory, but in practice they have the opposite effect.

Now, the convention you linked sounds reasonable for the most of it. I'd disagree with a couple of their suggestions, but that's just me. Naming conventions (just like "space vs tab", or "opening braces in their own line vs next to the block opening statement"), are down to personal preference. None of what they suggest is madness, it's all pretty reasonable and has a high degree of consistency (which is the important part of standards), and that already puts their conventions above a lot of others I've seen out there.

RE: sensible C++ coding convention - µOS naming standard

shabaz — Sun, 01 Sep 2024 19:41:06 GMT

Interesting stuff. I took a peek at the naming conventions you linked to, it makes sense, as well as the Industrial Strength C++ book. My C++ wasn't formally taught (I picked it up initially from an Aussie firm, and then did self-study with books - Stroustrup etc). I stuck with the conventions that firm used, which looks similarish to the Industrial Strength conventions it seems, e.g. capital on the class names, and using an 'm' for member variables, although back-to-front and lower-case, e.g. mPacketCount or whatever. Definitely good to stay consistent in a style.

RE: sensible C++ coding convention - µOS naming standard

DAB — Sun, 01 Sep 2024 18:59:27 GMT

Thanks Jan.

Naming conventions are always a good way to start a fight among software engineers.

While most people don't care, they just want to get the code done, you always run into a few fanatics who have their favorite and refuse to conform.

If you are just writing code for yourself you can do what you want, but as soon as you work with a team, you need everyone on board or chaos ensues.