I just wanted to point out that while
NaN should certainly not be written to a device,
*reading* NaN from a PV makes perfect sense to
me and is in fact a very useful and IMO legal way
to indicate e.g., that some numbers in an array
are invalid (while others may be good and it
hence doesn't make sense to mark the entire PV
status invalid).
IMO NaN should be handled at the source
(you restore program shouldn't try to send NaN)
and/or destination (don't write NaN to device)
but otherwise propagated (e.g. calc record)
-- Till
- References:
- RE: Not-a-number (nan) issues Jeff Hill
- Re: Not-a-number (nan) issues Kay-Uwe Kasemir
- Navigate by Date:
- Prev:
double defenition in Epics Liyu, Andrei
- Next:
Re: Not-a-number (nan) issues Andrew Johnson
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
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: Not-a-number (nan) issues Eric Norum
- Next:
Re: Not-a-number (nan) issues Andrew Johnson
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
<2004>
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|