The scheme for including leap seconds that I posted yesterday has been widely---by at least two readers---misunderstood. It or a functional equivalent must/should be used when the underlying time measurement is a TOD-clock [STCKE] value, an atomic-clock reading, or the like. It should NOT be used when this measurement is a TIME-macro based one. Such values already include leap-second corrections. To make them a second time would be otiose, and the result so obtained would be wrong.
Let me also exploit this post to note that glb-seeking and lub-seeking binary search are much more important than the traditional match-seeking binary-search schemes that appear---almost always badly implemented because phobic about ternary comparisons---in programming textbooks. John Gilmore, Ashland, MA 01721 - USA
