The meaning of version numbers can vary across projects.

One common scheme is Semantic Versioning, which divides the version number into three parts: MAJOR.MINOR.PATCH*

• MAJOR is incremented when there are backwards incompatible changes.
• MINOR is incremented when new features are added in a backwards compatible way.
• PATCH is incremented for smaller big fixes.
• Each number is reset to zero when a higher level number is incremented.

* It’s a bit more complex than this, but this is the gist.

OP here! People are rightfully pointing out that this can be compressed further.

My challenge to you: Implement a compressed representation along with the get_cell and set_cell methods, without resorting to lookup tables!

Also, check out Alejandra’s blog at https://goose.love/!

(And yeah, you need 12 or 13 bits, not 10, if you don’t want to eliminate symmetries.)

The GNU Coding Standards has a section on Make, which I would think is the most prominent Make style guide.

The doc itself doesn’t have a section on comments, but in the few examples given in that doc, they use style B.

https://www.gnu.org/prep/standards/html_node/Makefile-Conventions.html