If we are going to have a new general purpose subroutine record then I would
like to suggest one of the following.
1) Create a record type with multiple links. Each link has an associated value
field like the current subroutine record but in addition has
fields specifying the field type (DBF_STRING,...,DBF_ENUM) and the
number of elements. This allows the application developer to determine the
field type of each link and also allows each link to reference an array.
2) Create a record type with multiple links but dont let record support
do any I/O on the links. In addition the value fields can be declared
SPC_DBADDR. The subroutine can then be called whenever dbNameToAddr accesses
the field. The subroutine can then make the field any type it wants and can also
make it an array.
Note that in case 2 the subroutine can perform input and/or output on
each link. Allowing this may cause problems for tools like gdct and capfast.
Are the problems that bad?
Marty Kraimer
- Navigate by Date:
- Prev:
Re: EPICS status codes proposal watson
- Next:
Re: NT changes for 3.12.2 Chris Timossi
- 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: Subroutine record input fields don't get archived William Lupton
- Next:
Re: Subroutine record input fields don't get archived Steve Lewis
- 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
|