Android Question b4xlib manifest version numbers are strange

[Sandman]

I'm creating a b4xlib and try to set this kind of version in the manifest.txt:

Version=2.12-2020-01-23-11-31-19

So, basically, during the automated build process of the b4xlib a timestamp is added to the version number.

This is not appreciated by B4A:

(A somewhat vague error message, by the way - took some time figuring out what the problem was.)


While investigating this I found that the version field only allows for <number><dot><number, two figures max>. To make it even more strange, the last number was rounded:

This manifest...

Version=12.34567890

...shows as this:

Another example, as I tried to understand the limitations:

Version=1234567890.1234567890

Shows as:

Does anyone know what the actual specification for the Version field is?

 

[Erel]

The version should be a valid number.

 

[Sandman]

And what is the definition of "a valid number"? Because the ones below apparently aren't.

Version=12.34567890

Version=1234567890.1234567890

 

[Erel]

These are strange but valid numbers.
The IDE formats the numbers (you should never show unformatted numbers) with two decimal points.

 

[Sandman]

Looking closer it seems to be <int rounded to 7 figures><dot><int rounded to 2 figures>.

Can that be correct?

 

[Erel]

The number is a 4 byte floating point number. It will be less accurate with very large numbers.

 

[Sandman]

Understood, thanks. I'll scrap the idea to add a timestamp and just go with an increasing version number instead.