Insights Blog
-- Browse All Articles --
Physics Articles
Physics Tutorials
Physics Guides
Physics FAQ
Math Articles
Math Tutorials
Math Guides
Math FAQ
Education Articles
Education Guides
Bio/Chem Articles
Technology Guides
Computer Science Tutorials
Forums
Chemistry
Biology and Medical
Earth Sciences
Computer Science
Computing and Technology
DIY Projects
Trending
Featured Threads
Log in
Register
What's new
Search
Search
Search titles only
By:
Chemistry
Biology and Medical
Earth Sciences
Computer Science
Computing and Technology
DIY Projects
Menu
Log in
Register
Navigation
More options
Contact us
Close Menu
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Forums
Other Sciences
Computing and Technology
The Impact of Negative Leap Seconds: Risks and Challenges for IT Systems
Reply to thread
Message
[QUOTE="Vanadium 50, post: 6660474, member: 110252"] If you are using a well-vetted structure, like time_t, and well-vetted routines like difftime, what you suggest will work. The problem apparently is that people don't use difftime(time_t x, time_t y) for the difference between the times x and y, but rather roll their own. As you say, NTP handles this fine, and it deals with clocks that are too far ahead millions of times each day with no problems. The difficulty seems to be that some code where time-keeping is missionm critical a) bypass NTP, and b) bypass the well-vetted and built-in functionality described above. Bad choices produce bad outcomes. [/QUOTE]
Insert quotes…
Post reply
Forums
Other Sciences
Computing and Technology
The Impact of Negative Leap Seconds: Risks and Challenges for IT Systems
Back
Top