Re: ezca and ENUM

["D. Peter Siddons" <siddons@bnl.gov>]

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