Dear all,
Marty wrote:
> Also think of precedent being set. Will we have an endless set of
> xxxwarn attributes for each field description?
Fair comment.
> Note also that the warning message is telling the application engineer
> that he/she has given a value that will not appear as specified in the
> database. It really is a database configuration error.
I had assumed that the default DESC strings were somehow in base, but in
fact I think this is not the case: the defaults are in the Capfast symbols.
Perhaps we should at least ensure that none of the default DESC strings in
the symbols exceeds the limit and triggers the warning?
Finally, I can't help following Andy's lead and asking why there is no
record field that indicates the record type. I believe that this could
often be useful. What about RTYP?
William
- Replies:
- Re: EPICS r3.13 field DESC length Marty Kraimer
- Navigate by Date:
- Prev:
Re: Hideos - Future Tim Mooney
- Next:
Re: EPICS r3.13 field DESC length Marty Kraimer
- 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: EPICS r3.13 field DESC length Andy Foster
- Next:
Re: EPICS r3.13 field DESC length Marty Kraimer
- 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
|