http://bugzilla.wpkg.org/show_bug.cgi?id=120 Malte Starostik <malte at malte.homeip.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |malte at malte.homeip.net --- Comment #13 from Malte Starostik <malte at malte.homeip.net> 2009-06-15 20:35:21 --- (In reply to comment #8) Usually a > version is assumed to be higher if it has an additional suffix but in case > of RC (Release Candidate), M (Milestone) and I (Integration) releases it's > usually the opposite way around. Never heard of "Integration", but things like "1.0b5", "1.0beta5", "1.0_beta5" etc come to mind. same goes for alpha. (In reply to comment #10) > 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 That's because parseInt() parses the number similarly to (or exactly like?) a C compiler or strtol() with a zero base: "099" is treated as an octal number because of the leading zero. But 9 is not a valid octal digit and thus the parsing stops right after the 0. parseInt() has an optional second argument to specify the number's radix: parseInt("010") => octal 10 => decimal 8 parseInt("010", 10) => decimal 10 Regards, Malte -- Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. |