@Freddie, I guess that's good enough going forward.
> ... print a warning message on any machine where the counter could wrap?
Like "warning: your IOC will stop working in 49 days"? Were it my IOC, I'd rather have a build failure than an easily overlooked "warning" like this. Still, I've put XP behind me, so happily this doesn't much matter to me personally. My only concern is that leaving GetTickCount() around in a conditional opens the possibility of a regression if the logic is, or becomes, wrong.
--
https://code.launchpad.net/~freddie-akeroyd/epics-base/+git/epics-base/+merge/391018
Your team EPICS Core Developers is requested to review the proposed merge of ~freddie-akeroyd/epics-base:fix_win32_monotonic_time into epics-base:7.0.
- References:
- [Merge] ~freddie-akeroyd/epics-base:fix_win32_monotonic_time into epics-base:7.0 Freddie Akeroyd via Core-talk
- Navigate by Date:
- Prev:
Re: [Merge] ~freddie-akeroyd/epics-base:fix_win32_monotonic_time into epics-base:7.0 Freddie Akeroyd via Core-talk
- Next:
[Bug 1896295] Re: WIN32: IOC scan loops hang mdavidsaver via Core-talk
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
<2020>
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: [Merge] ~freddie-akeroyd/epics-base:fix_win32_monotonic_time into epics-base:7.0 Freddie Akeroyd via Core-talk
- Next:
Re: [Merge] ~freddie-akeroyd/epics-base:fix_win32_monotonic_time into epics-base:7.0 Freddie Akeroyd via Core-talk
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
<2020>
2021
2022
2023
2024
|