Experimental Physics and Industrial Control System
On 5/18/11 7:21 AM, Dirk Zimoch wrote:
> Therefore I propose to remove all *MustSucceed functions from
> future EPICS releases and allow and require proper error
> handling by the application.
>
> Any opinions on this topic?
Hi, Dirk.
What about the *MustCreate, *MustWait, and *MustLock functions?
epicsEventMustCreate
epicsEventMustWait
epicsMutexMustCreate
epicsMutexMustLock
epicsThreadMustCreate
On a related note, I didn't look at all of them, but some of
these (e.g. epicsEventMustWait) are implemented as macros that
just do an assert on the return status of the regular non-must
function. Others (e.g. POSIX epicsEventMustCreate) are actual
functions, but they too just do an assert. If assertions are
disabled, this will do nothing and hence seems broken to me. No?
Lewis
- Replies:
- Re: caGateway crashes / use of *MustSucceed functions Dirk Zimoch
- Re: caGateway crashes / use of *MustSucceed functions Benjamin Franksen
- References:
- caGateway crashes / use of *MustSucceed functions Dirk Zimoch
- Navigate by Date:
- Prev:
Re: caGateway crashes / use of *MustSucceed functions Michael Davidsaver
- Next:
Re: alh1_2_24 build problem Andrew Johnson
- 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
- Navigate by Thread:
- Prev:
Re: caGateway crashes / use of *MustSucceed functions Michael Davidsaver
- Next:
Re: caGateway crashes / use of *MustSucceed functions Dirk Zimoch
- 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