Experimental Physics and
Industrial Control System

Kay-Uwe Kasemir <[email protected]> · Tue, 02 Aug 2005 14:25:15 -0400

On Jul 29, 2005, at 18:44, Ralph Lange wrote:

The Gateway needs to understand the data.
We have to nail the basic types down.

OK. Is this the list:
  bool
  octet
  int (16, 32, 64 bits)
  float  (32, 64)
  string
  enum
  timestamp
plus structures and arrays built from the basic types?

I would rather not call these types "network" types because they are

mandatory for DataAccess even if there is no network involved.

Marty started epicsTypes, EpicsBuffer, ...
I like this idea of 'EPICS Data' to describe data wherever possible,
but would prefer interfaces instead of a struct/interface/class mix.

I would prefer the type info thing to be a struct (type, bitwidth,

...) rather than a large enum.

Does the "EpicsDataDescriptor" interface from
   http://www.aps.anl.gov/epics/wiki/index.php/V4_Data_Interface
with getType(), getBitsize(), ... match what you'd like to see?
Or does a struct { type, bitwidth, ... } have advantages?

Thanks,
-Kay

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System