lmi-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[lmi-commits] [lmi] master 8fd99ca: Update documentation


From: Greg Chicares
Subject: [lmi-commits] [lmi] master 8fd99ca: Update documentation
Date: Thu, 19 Aug 2021 07:57:03 -0400 (EDT)

branch: master
commit 8fd99ca1c218d76f81925fd9d3370603f668f9d9
Author: Gregory W. Chicares <gchicares@sbcglobal.net>
Commit: Gregory W. Chicares <gchicares@sbcglobal.net>

    Update documentation
    
    Noted a MinGW-w64 defect.
    
    Removed a criticism of boost which they had later rectified.
---
 timer.hpp | 10 ++++------
 1 file changed, 4 insertions(+), 6 deletions(-)

diff --git a/timer.hpp b/timer.hpp
index c6bb760..5f19107 100644
--- a/timer.hpp
+++ b/timer.hpp
@@ -37,12 +37,10 @@ void lmi_sleep(int seconds);
 
 /// Why another timer class?
 ///
-/// Boost provides a timer class, but they deliberately chose to use
-/// only a low-resolution timer. Their rationale is apparently that
-/// high-resolution timers may be more precise than they are accurate,
-/// and that latency is a significant concern. This class uses a high-
-/// resolution timer if available; it's a sharp tool that lets you
-/// make your own decision about that rationale.
+/// Since C++11, std::chrono::high_resolution_clock ought to make this
+/// redundant. However, MinGW-w64's implementation is defective--see:
+///   https://lists.nongnu.org/archive/html/lmi/2021-08/msg00007.html
+///   https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63400
 
 class LMI_SO Timer
 {



reply via email to

[Prev in Thread] Current Thread [Next in Thread]