| 2002 2003 2004 2005 2006 <2007> 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 | Index | 2002 2003 2004 2005 2006 <2007> 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | Re: AppDevGuide not up-to-date on devLib |
| From: | Andrew Johnson <[email protected]> |
| To: | [email protected] |
| Cc: | [email protected] |
| Date: | Mon, 05 Feb 2007 15:32:20 -0600 |
Benjamin Franksen wrote:
It seems the current AppDevGuide doesn't document the routines devReadProbe, devNoResponseProbe, and devWriteProbe (chapter 20.18 Device Support Library). Furthermore, the documentation for the devLib routines does not say anything about what the return values of the several routines mean.
Since I'm not responsible for maintaining devLib I didn't want to spend much time on this, but I have added most of the current devLib.h routines to the final R3.14.9 AppDevGuide with some rudimentary text where appropriate.
If the return value is a long and the meaning is not described, most EPICS routines will give back a status value of some kind, where 0 means Ok and anything else is an error. I have no idea where this should be documented, especially since none of the errSymLib.c routines are covered anywhere...
- Andrew -- The right to be heard does not automatically include the right to be taken seriously. -- Hubert H. Humphrey