| commit | 16825b1a828bb4ff40f7682040e43a239b7b8ca3 | [log] [tgz] |
|---|---|---|
| author | pkasting@chromium.org <pkasting@chromium.org> | Mon Jan 12 21:51:21 2015 +0000 |
| committer | pkasting@chromium.org <pkasting@chromium.org> | Mon Jan 12 21:51:21 2015 +0000 |
| tree | 870180ec53908b93287857f58b963ff05b29f4ec | |
| parent | a7add19cf4dfce4ebe7e4ed24da3e1c49d5ddcc1 [diff] |
Use int64_t more consistently for times, in particular for RTT values. Existing code was inconsistent about whether to use uint16_t, int, unsigned int, or uint32_t, and sometimes silently truncated one to another, or truncated int64_t. Because most core time-handling functions use int64_t, being consistent about using int64_t unless otherwise necessary minimizes the number of explicit or implicit casts. BUG=chromium:81439 TEST=none R=henrik.lundin@webrtc.org, holmer@google.com, tommi@webrtc.org Review URL: https://webrtc-codereview.appspot.com/31349004 git-svn-id: http://webrtc.googlecode.com/svn/trunk@8045 4adac7df-926f-26a2-2b94-8c16560cd09d