Re:Implement mechanism to wait on any of several futexes
by scohesc on Wednesday July 31, 2019 @12:04PM
(#20575517)
Am I interpreting the graph on their page all wrong? It looks like the older version of Proton provides better performance? Unless they're graphing function call return time? The graph and the text around it doesn't do a good job of explaining that.
[ Parent
| on HN ]
Re:Implement mechanism to wait on any of several futexes
by GranPC on Wednesday July 31, 2019 @12:06PM
(#20575533)
4.11 is newer than 4.2
Re:Implement mechanism to wait on any of several futexes
by geddy on Wednesday July 31, 2019 @12:50PM
(#20575979)
I have no idea why this took me so long to realize. Must be the versions I'm used to seeing but my brain parsed `4.11` as `4.1.1`. Weird.
Thanks for pointing out the obvious for those of us who missed it!
Re:Implement mechanism to wait on any of several futexes
by falcrist on Wednesday July 31, 2019 @01:29PM
(#20576388)
You parse it the same way I usually do. As a decimal fraction, 4.2 > 4.11... however, version numbers aren't decimal fractions.
In any case, you're not alone.
Re:Implement mechanism to wait on any of several futexes
by belltaco on Wednesday July 31, 2019 @12:06PM
(#20575537)
4.11 is 9 versions newer than 4.2
Re:Implement mechanism to wait on any of several futexes
by sjwright on Wednesday July 31, 2019 @12:09PM
(#20575562)
The thing to remember is that version numbers aren’t decimals. They’re two or three integers separated by periods.
11 is higher than 2.
Re:Implement mechanism to wait on any of several futexes
by rimunroe on Wednesday July 31, 2019 @12:17PM
(#20575641)
I don't know what the source of this convention is, but this is why I was taught that the version "1.2.3" should be read aloud as "one dot two dot three" instead of "one point two point three". The idea is that people--where I'm from at least--tend to read decimals as "point" and not "dot".
Re:Implement mechanism to wait on any of several futexes
by sjwright on Wednesday July 31, 2019 @10:33PM
(#20580692)
Yes, sadly the proliferation of the "two point oh" meme has set society back on that front. (Had we the opportunity to start over, I would have proposed different punctuation for the delimiter to avoid natural confusion with decimals.)
Re:Implement mechanism to wait on any of several futexes
by kleer001 on Wednesday July 31, 2019 @12:15PM
(#20575619)
Harumph. Then it should be padded with zeros. So, 4.002 and 4.011
/grumpy
edit: nope, it's fine as is. my experience in frame numbers, dates, and so forth do not scale to releases
Re:Implement mechanism to wait on any of several futexes
by wongarsu on Wednesday July 31, 2019 @12:43PM
(#20575905)
4.0.0 (semver) and 4.0.0.0 (Windows) aren't valid numbers anyways; The confusion can only arise on X.Y version numbers. Just add a .0 at the end of those
Re:Implement mechanism to wait on any of several futexes
by golergka on Wednesday July 31, 2019 @12:24PM
(#20575715)
But why? You don't know how many decimals you'll need in advance - three digits isn't enough for Windows build number, for example.
Re:Implement mechanism to wait on any of several futexes
by kinleyd on Wednesday July 31, 2019 @12:25PM
(#20575725)
Some years ago I thought so too. Now I'm just used to it.
Re:Implement mechanism to wait on any of several futexes
by wiml on Thursday August 01, 2019 @12:54PM
(#20585766)
Dates are the same, though — 01.15.2018 is not a real number, it's a sequence of integers. (And in many places they're not even written in most-to-least or least-to-most significant order! …I guess that makes it a tuple, not a sequence.)