This is Issue 959 moved from a Google Code project.
Added by 2012-06-17T06:50:02.000Z by xolr...@gmail.com.
Please review that bug for more context and additional comments, but update this bug.
Closed (WontFix).
Original labels: Type-Enhancement, Priority-Medium
Original description
When millis() and micros() roll over, there is currently no way to let your program notice, other than storing it in a variable and comparing every loop, which uses up precious clock cycles. You could simply have a hardware variable that increments every time millis() rolls over, and another one that increments every time micros() rolls over.
This is Issue 959 moved from a Google Code project.
Added by 2012-06-17T06:50:02.000Z by xolr...@gmail.com.
Please review that bug for more context and additional comments, but update this bug.
Closed (WontFix).
Original labels: Type-Enhancement, Priority-Medium
Original description
When millis() and micros() roll over, there is currently no way to let your program notice, other than storing it in a variable and comparing every loop, which uses up precious clock cycles. You could simply have a hardware variable that increments every time millis() rolls over, and another one that increments every time micros() rolls over.