Andrew Johnson wrote:
>
> While I was away on vacation, Bob Dalesio wrote:
> >
> > Also, the LINR field is an enum. Having it be an enum for
> > anything it finds and an arbitrary string if it is not
> > located, is not supported. When we connect to CA, the field
> > primatives cannot be mixed.
>
> LINR might be converted to a string field, which would allow the desired
> behaviour (and permit the addition of new breakpoint tables at run-time).
> Another problem with the enum is that it really should be dynamic
> according to the breakpoint tables actually loaded into the IOC, but it
> isn't. However switching to a string will probably break some existing
> databases and displays, so I expect it to be rejected.
I have thought about a different solution. Reduce menuConvert to a fixed
set of general conversion methods, i.e. one of {NO CONVERSION, LINEAR,
BREAKPOINT, SUBROUTINE}. A separate (new) field of string type could
hold the name of the breakpoint table in case LINR is BREAKPOINT or the
name of a subroutine in case LINR is SUBROUTINE.
Ben
- Replies:
- Re: Apropos making fields configurable Andrew Johnson
- References:
- Re: Apropos making fields configurable Bob Dalesio
- Re: Apropos making fields configurable Andrew Johnson
- Navigate by Date:
- Prev:
Re: Apropos making fields configurable Andrew Johnson
- Next:
VxWorks kernel configuration for GPIB Robert Willson
- 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: Apropos making fields configurable Andrew Johnson
- Next:
Re: Apropos making fields configurable 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
|