Experimental Physics and
Industrial Control System

"Jeff Hill" <[email protected]> · Mon, 1 Nov 2010 09:02:41 -0600

> Oops. I have not looked close enough. The C and C++ interfaces differ in
> the return value. The C++ methods really return bool, whereas the C
> routines return the epicsEventWaitStatus. Am I the only one who finds
> this confusing? 

It hasn’t been an issue for me

> What happens if the C++ method encounters an error?

It throw an exception. It is very typical for C++, and 
Java, interfaces to throw an exception when there is an 
error

Jeff
______________________________________________________
Jeffrey O. Hill           Email        [email protected]
LANL MS H820              Voice        505 665 1831
Los Alamos NM 87545 USA   FAX          505 665 5107

Message content: TSPA

With sufficient thrust, pigs fly just fine. However, this is
not necessarily a good idea. It is hard to be sure where they
are going to land, and it could be dangerous sitting under them
as they fly overhead. -- RFC 1925

> -----Original Message-----
> From: [email protected] [mailto:[email protected]]
> On Behalf Of Ben Franksen
> Sent: Friday, October 29, 2010 7:49 PM
> To: [email protected]
> Subject: Re: epicsEvent semantics
> 
> On Samstag, 30. Oktober 2010, Ben Franksen wrote:
> > On Freitag, 29. Oktober 2010, Andrew Johnson wrote:
> > > On Friday 29 October 2010 14:15:54 Ralph Lange wrote:
> > > >   On 29.10.2010 15:10, Eric Norum wrote:
> > > > > +dded to epicsEventTest and the application developers guide
> > > > > has been updated +to describe this requirement.</p>
> > > >
> > > > Did you actually update the guide? At least I don't see it on
> > > > launchpad yet...
> > >
> > > Working on it, I have some uncommitted formatting changes that I
> > > want to keep separate that I'm also dealing with.
> >
> > While you're at it, please fix the description for wait and tryWait,
> > they are most probably wrong. What is returned is an
> > epicsEventWaitStatus, not boolean. When interpreted as boolean the
> > return value is zero (false) if the event *did* happen
> > (epicsEventWaitOK) and non-zero (true) if it did not happen
> > (epicsEventWaitTimeout) or if an error happened
> > (epicsEventWaitError). At least this is what the names suggest.
> 
> Oops. I have not looked close enough. The C and C++ interfaces differ in
> the return value. The C++ methods really return bool, whereas the C
> routines return the epicsEventWaitStatus. Am I the only one who finds
> this confusing? What happens if the C++ method encounters an error?
> 
> Cheers
> ben

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System