Come Dancing

In the ‘Come Dancing’ tv prog – results are given as 0-10

It would be useful to add a point ie 5.5 6.3 to the results.

Same would apply to updated RO progs ie 0.12 to 0.121 etc.

Conflating scores with (I guess?) versions is making my brain bleed, but Module version numbers (and hence OS version numbers) ARE ALREADY four decimal digits.

So 0.1201 is perfectly possible.

And this is not frivolous, e.g. the VDUVertical module is based on Unicode 13.0 data, so its version number must be 13.0xxx to reflect that, so what would otherwise be revision 1.23 of the code would become 13.0123.

Conflating module versions with Unicode versions makes my head hurt.

Can we please not end up like browser versions where it’s v1.23.456.7a8fg.357.rc2 or somesuch.

It’s probably a side effect of agile development that there aren’t really versions as we know them, more a never-ending set of “this isn’t the same build as yesterday”.
In which case, a big endian date suffix would probably be better…

Conflating module versions with Unicode versions makes my head hurt.

No choice when you have multiple modules containing parts of a Unicode standard – if you try using this table from this version of the standard with that table from that other version, you’ll get odd results in extremis. So Unicode version is the most important part (and you’d expect the code to stay pretty static even while the data changes over time).

v1.23.456.7a8fg.357.rc2

Which is also a valid Module version string.

It’ll get reported as (effectively) 1.2300 but it’s valid, as long as it doesn’t start before the 16th column when formatted by PrettyPrint [I wish I were joking about that, but I’m not].