[wpkg-users] [Bug 120] Enhanced revision check and handling

[bugzilla-daemon at bugzilla.wpkg.org]

http://bugzilla.wpkg.org/show_bug.cgi?id=120





--- Comment #10 from Rainer Meier <r.meier at wpkg.org>  2009-06-15 18:25:05 ---
Oh no... this was unexpected. Looks like this case hit a strange behavior of
the parseInt() method used internally.
parseInt(099) results in integer 0 (??)
while
parseInt(99) correctly resolves to 99

Removing of leading zeroes could have fixed this and have 099 recognized to be
different to 0.9.9 (which I would have expected acutually even for the previous
algorithm.

However the old algorithm was extremely simple and there could be more case
where it fails.
I just see that also the new algorithm could produce unexpected results in some
cases - but this time using much much more complicated special cases (which
hopefully do not occur that often). So at least simple cases should be
evaluated perfectly. My personal recommendation is still to use just a
colon-separated sequence of numbers. Have a look at the examples which lists a
lot more advanced versions which "should" be evaluated correctly. But the case
with "RC" where the appendix indicates a pre-release instead of an update to
the release is a special case. Unfortunately I cannot excuse myself here to say
this is an unusual case since I am using the RC-approach myself ;-)

-- 
Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.