OK. I think that A..U should be enough for now.
Thanks,
Kate
On 09/14/2012 10:50 AM, Andrew Johnson wrote:
Hi Kate,
On 2012-09-14 Kate Feng wrote:
Adding arguemnts to the aSub record would facilitate the usage of
the subroutine to
be more globally generic and versatile. The arguments will be used for
the subroutine.
I don't really understand the purpose of these. The subroutine already has
direct access to the 21 type-configurable input fields A..U that can be read
from the links INPA..INPU and which are more flexible, why can't it use those
instead?
The aSub record already has 284 fields, 48 of which are links, so each
instance of an aSub record takes up something like 4000 bytes (a bit less on a
32-bit CPU) without including the array storage. If you want a record type
with a different interface to the subroutine you're welcome to create one and
publish it, but I don't currently see this addition to the aSub making it into
Base without more explanation and a stronger case for it.
- Andrew
- References:
- aSub record : adding arguments Kate Feng
- Re: aSub record : adding arguments Andrew Johnson
- Navigate by Date:
- Prev:
Re: waveform changes using subArray Hinko Kocevar
- Next:
RE: How to profile an EPICS application on Linux Mark Rivers
- 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: aSub record : adding arguments Andrew Johnson
- Next:
Question on configuring soft IOC server ports Mark Rivers
- 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
|