Noboru,
That is correct: the FNAL Python/EPICS API does use SWIG to generate
the interface.
Fritz
Noboru Yamamoto wrote:
Hi,
D. Peter Siddons wrote:
The Python interface does not start from
ezca; does it have the same difficulties/restrictions? Maybe we should
start from raw ca?
Pete.
As far as I remember, FNAL version of EPICS-Python interface uses
SWIG(Simple Wrapper Interface Generator). It maps C/C++ API interface
into Python API. KEK version of EPICS-Python interface was written from
scratch, and it also maps C APIC for EPICS CA to Python API, but not
all. You can build your own Python module to hide the raw CA API,
which may work similar to EZCA.
Most of Python application in KEKB uses Tkinter(Tcl/Tk widget
interface for Python) and EPICS CA. And the most of channels in these
applications are monitored, so that no need to wait fixed pend-io time.
If user likes to use Python-equivalent of a raw CA API, it is also
possible.
Noboru Yamamoto
EPICS group/J-PARC control group
KEK, JAPAN
--
J. Frederick Bartlett
Fermi National Accelerator Laboratory
D0 Experiment/Controls
[email protected]
630-840-4058
|
