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 | 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 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: Matlab interfaces |
From: | Noboru Yamamoto <[email protected]> |
To: | "D. Peter Siddons" <[email protected]> |
Cc: | Till Straumann <[email protected]>, "Allison, Stephanie" <[email protected]>, Korhonen Timo <[email protected]>, [email protected] |
Date: | Wed, 05 Jul 2006 08:17:25 +0900 |
The Python interface does not start from ezca; does it have the same difficulties/restrictions? Maybe we should start from raw ca?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,
Pete.
Noboru Yamamoto EPICS group/J-PARC control group KEK, JAPAN