Subject: |
Re: Unexpected change in behaviour of ai/ao device support |
From: |
Ralph Lange via Tech-talk <[email protected]> |
To: |
EPICS Tech Talk <[email protected]> |
Date: |
Tue, 11 Jun 2019 10:28:45 +0200 |
Hi Michael,
Use of the ROFF field has been effectively deprecated since 1998, when its functionality was taken over by the cleaner ESLO/EOFF mechanism. ROFF was mainly kept for compatibility reasons.
I am sorry for the inconvenience caused by this change. However, I think that not having many users being affected might be related to the ROFF deprecation 17 years before.
All this has not been adequately reflected in the Record Reference Manual, for sure. In the current documentation (that is part of the sources), field types are correct.
Cheers, ~Ralph
- Replies:
- Re: Unexpected change in behaviour of ai/ao device support Johnson, Andrew N. via Tech-talk
- References:
- Unexpected change in behaviour of ai/ao device support michael.abbott--- via Tech-talk
- Navigate by Date:
- Prev:
EPICS June 2019 Meeting talks are on-line Ralph Lange via Tech-talk
- Next:
Re: Unexpected change in behaviour of ai/ao device support Johnson, Andrew N. via Tech-talk
- 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
2025
- Navigate by Thread:
- Prev:
Unexpected change in behaviour of ai/ao device support michael.abbott--- via Tech-talk
- Next:
Re: Unexpected change in behaviour of ai/ao device support Johnson, Andrew N. via Tech-talk
- 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
2025
|