Experimental Physics and Industrial Control System
|
Hi Andrew,
Yes, a string would work as well, but I was writing the Octave
wrappers for ezca which I'd like to make self-contained and general.
This implies asking the record what type it is in order to make calls
with the correct type. It would be nice if valid types were treated as
such by the library :) As it is, I trap the ENUM type in my wrapper and
turn it into a SHORT, and all is well. But it hides what I feel is a bug.
Pete.
Andrew Johnson wrote:
D. Peter Siddons wrote:
I noticed that the ezca library does not recognize ENUM as a valid
data type. One can work around that by telling it to use a SHORT
instead. If
Would it help to use string data for doing I/O to DBF_ENUM fields? That
way you don't need to know the exact ENUM definition (which could change
at runtime even for mbbx.VAL fields); your code just uses the strings
for the states that you need to use, and the IOC does the necessary
conversions automatically.
Just an idea,
- Andrew
- References:
- ezca and ENUM D. Peter Siddons
- Re: ezca and ENUM Andrew Johnson
- Navigate by Date:
- Prev:
Re: ezca and ENUM Andrew Johnson
- Next:
RE: NetBSD: implementation of"osiSockDiscoverInterfaceAddresses()" Jeff Hill
- 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: ezca and ENUM Andrew Johnson
- Next:
RE: ezca and ENUM 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
|
ANJ, 02 Sep 2010 |
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
·
Search
·
EPICS V4
·
IRMIS
·
Talk
·
Bugs
·
Documents
·
Links
·
Licensing
·
|