Hi Dirk,
On 02/08/2018 07:23 AM, Dirk Zimoch wrote:
> Attached is a patch file for dbScan.c which should fix the problem and
> restore backward compatibility.
>
> I have created (and quickly tested) it with EPICS 7 but I guess it
> should work with 3.16 as well.
Please work against the 3.15 branch, since that was where we introduced
your named events work. We will merge it up into the later branches from
there.
> The hack is to treat "x.000000" and "x" as the same event name if x is
> an integer between 0 and 255. ("0" and "0.000000" are no event at all
> now just like "").
I don't like the string comparisons since they would silently break if
the number of decimal digits generated by the double → string conversion
gets changed.
Better to parse the string properly into a double — look at the
epicsParseDouble() routine declared in epicsStdlib.h and documented at
https://epics.anl.gov/base/R3-15/5-docs/AppDevGuide/libComOSIlibraries.html#x21-84700020.13
— then either round or truncate the fractional part.
Thanks,
- Andrew
--
Arguing for surveillance because you have nothing to hide is no
different than making the claim, "I don't care about freedom of
speech because I have nothing to say." -- Edward Snowdon
- Replies:
- Re: Scanning on event number fails with EPICS 3.16 Dirk Zimoch
- Re: Scanning on event number fails with EPICS 3.16 Dirk Zimoch
- Re: Scanning on event number fails with EPICS 3.16 Dirk Zimoch
- Navigate by Date:
- Prev:
Re: Epics Core 7 & Submodules Hugo Slepicka
- Next:
Re: Scanning on event number fails with EPICS 3.16 Dirk Zimoch
- 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: Epics Core 7 & Submodules Hugo Slepicka
- Next:
Re: Scanning on event number fails with EPICS 3.16 Dirk Zimoch
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
<2018>
2019
2020
2021
2022
2023
2024
|