Hmmm. This has just set me thinking. My original Performa 400 came with 7.1p. Are we saying it was actually 7.1.2p, but About This Macintosh.. just displayed "7.1P"?
I've lost count of the number of companies I've worked at which screwed up version control for embedded products, leading to a lack of version numbers and consequently real maintenance issues that cost the company money. For example, using 2 bytes for version numbers, and then crippling them further by encoding them in ASCII! ("99 versions should be enough for anyone"); finding they were already up to 9.8 by the time I arrived and still absolutely refusing to give themselves 5-digits of breathing space by switching over to a literal integer encoding!!! ("9.8" encoded as { 0x49, 0x48} which in big-endian decimal (not BCD) is: 18760. So all you need to do is defined every version number above 18760 as the (value-18760)/10000+9.9. This means 65535=>14.5.7b75. We can allocate up to 5 more major versions, with a 1 digit feature version, 1 digit bug-fix and 2 digit build numbers. Then dev builds and candidate builds won't get confused and if there's a feature update every 6 months, we have 50 more years of version numbers left.