Hi Tim,
> I wouldn't want to say "never". If the data are going to end up in
> Python variables, I'd agree that DBR_SHORT and DBR_INT, for example,
> are unnecessary complications. But if I had to read a very large
> array of two-byte integers, and hand the array off to some other
> code that expects an array of two-byte integers, I would need at
> minimum some way of specifying that two-byte integers be sent.
That's fair. I do agree that being able to get the underlying CA type
might be necessary (as in this case), and the native CA type should
certainly be available to anyone who wants to use it. I am
definitely not opposed to a wrapper that is "thin, complete", I just
think it's not enough. And I think that most (and perhaps all) of the
extras I've come to rely on can be layered on top of a thin wrapper.
--Matt Newville <newville at cars.uchicago.edu>
- References:
- Re: EPICS Python client application survey Matt Newville
- Re: EPICS Python client application survey Tim Mooney
- Navigate by Date:
- Prev:
RE: EPICS Python client application survey michael.abbott
- Next:
state notation code flags Patrick Thomas
- 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 Python client application survey Tim Mooney
- Next:
Re: EPICS Python client application survey Matt Newville
- 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
|