Ruakij/Geigercounter
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Check clock_t clock() and measurements to still be able to use nextTick #4

New Issue
Closed
opened 2019-03-05 14:14:28 +01:00 by Ruakij · 1 comment
Ruakij commented 2019-03-05 14:14:28 +01:00 (Migrated from gitea.railduction.eu)
Copy Link

clock() returns a clock_t. (maybe longint?)

This always counts up, but probably has an overflow at some point and will start over again.
Measures are needed even then to calculate the correct tick distance

clock() returns a clock_t. (maybe longint?) This always counts up, but probably has an overflow at some point and will start over again. Measures are needed even then to calculate the correct tick distance
Ruakij commented 2019-03-07 14:09:21 +01:00 (Migrated from gitea.railduction.eu)
Copy Link

There is no clock!

There is no clock!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something is not working
Critical
duplicate
This issue or pull request already exists
enhancement
New feature
help wanted
Need some help
Higher
invalid
Something is wrong
Normal
question
More information is needed
Todo
This is to do
wontfix
This won't be fixed
No Label
Normal
Todo
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Ruakij
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Ruakij/Geigercounter#4
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?