Hi Andrew,
> Then epicsThreadSleepQuantum() should return 0 in that case — the
> AppDevGuide says:
>> If this parameter is unknown or is unpredictable for a particular
>> OS then it is safe to return zero.
I understand that and it sounds reasonable. The problem is that I have
no idea how to detect if _SC_CLK_TCK makes sense or not. Without a way
to detect this, epicsThreadSleepQuantum() will return a wrong value on
modern Linux machines. I can think of two options:
1. Consider the value unknown on _all_ Linux machines. Modify
epicsThreadSleepQuantum() such that it _always_ returns 0 on Linux.
2. Leave epicsThreadSleepQuantum() as is and mark it deprecated to make
it obvious to developers that they are using something that might now
work as designed anymore.
-Martin
--
Martin Konrad
Facility for Rare Isotope Beams
Michigan State University
640 South Shaw Lane
East Lansing, MI 48824-1321, USA
Tel. 517-908-7253
Email: [email protected]
- Replies:
- RE: epicsThreadSleep and epicsThreadSleepQuantum Mark Rivers via Core-talk
- References:
- epicsThreadSleep and epicsThreadSleepQuantum Konrad, Martin via Core-talk
- Re: epicsThreadSleep and epicsThreadSleepQuantum Konrad, Martin via Core-talk
- RE: epicsThreadSleep and epicsThreadSleepQuantum Mark Rivers via Core-talk
- Re: epicsThreadSleep and epicsThreadSleepQuantum Michael Davidsaver via Core-talk
- Navigate by Date:
- Prev:
Jenkins build is back to normal : 3.15-normativeTypes-win64s #128 APS Jenkins via Core-talk
- Next:
RE: epicsThreadSleep and epicsThreadSleepQuantum Mark Rivers 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: epicsThreadSleep and epicsThreadSleepQuantum Johnson, Andrew N. via Core-talk
- Next:
RE: epicsThreadSleep and epicsThreadSleepQuantum Mark Rivers 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
|