It's all about the answers!

Ask a question

Version number formatting

David Ng (1665) | asked Oct 24 '11, 8:23 p.m.
We are on RAM v7.5. Help page / infocenter ( that creates a number of confusion / questions for us:

1) Does RAM understand 'One' as numeric 1. How does it know that MilestoneThree is after MilestoneTwo?
2) If the answer to (1) is true, then how does RAM differentiate between a name "One" from number "One"?
3) Should we avoid using padded zero in version number because RAM will treat them as strings?
4) What is the heuristics that apply to version number? based on ascii sequence?

Why do we want to know? Because we want to build a function to determine the latest version for a given asset. Therefore, we would like to know how RAM works in this regards.



One answer

permanent link
Rich Kulp (3.6k38) | answered Oct 25 '11, 10:26 a.m.

RAM doesn't understand spelling of numbers. The only format it
understands is:


Where 999 are any number of digits, and ... means repeating groups of

What it does is break it down into groups of digits separated by
periods. The first non-digit, non-period it finds terminates the break
of groups of digits.

It then orders by each group, first all ordered by the first group of
digits, then for those that have the same first group of digits are
ordered by the second group. For all that have the same first and second
group of digits they are then ordered by the third. And so on. And then
finally those that have all the same groups of digits are then ordered
in the current users locale's standard collation of the characters. I.e.
N > M > L. This since it is using UTF characters collation this will
take into account non-ascii also.

Don't pad with zeroes because then the numbers will be in radix 8 (octal).

Rich Kulp
Rational Asset Manager developer

Your answer

Register or to post your answer.