| 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 <2018> 2019 2020 2021 2022 2023 2024 | Index | 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 <2018> 2019 2020 2021 2022 2023 2024 |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | Re: Scanning on event number fails with EPICS 3.16 |
| From: | Ralph Lange <[email protected]> |
| To: | EPICS Core Talk <[email protected]> |
| Date: | Fri, 9 Feb 2018 11:00:22 +0100 |
The logic I am implementing now is:
If the string looks like a plain double (epicsParseDouble() succeeds and units[0]=='\0') and event >= 0.0 and event < 256.0 treat it as a numeric event: Round down to integer. Event number == 0 is no event.
Numeric events can be used with post_event() which is not tagged "deprecated" any more.
At the moment, I have three cases of "no event at all":
* NULL No event name
* "" Empty event name
* [0.0 - 1.0[ Numeric event number 0
In particular, "2", "0x02", " 2.000000", "2.99999 " and " 200e-2 " are the same event now.
"0", "0.00000", "0.99999", "-0" are no event.
"-2", "-0.00001", "256", "0x100", "256 ", " 256" are different named events.
I consider ignoring leading and trailing blanks, making "X Y", " X Y", and "X Y " the same and making " " no event.
What do you think?