[omniORB] CORBA::CompletionStatus

[Karel Gardas]

On Mon, 4 Nov 2002, Duncan Grisby wrote:

> On Monday 4 November, p.klotz@icoserve.com wrote:
>
> > Shouldn't CORBA::CompletionStatus according to the CORBA standard be
> > CORBA::completion_status?
>
> You would think so by reading the ORB Interface chapter, but if you
> look at the C++ mapping spec, you'll see that it should be
> CompletionStatus, so omniORB is correct. The Python mapping uses
> completion_status.
>
> > I ran into this problem when porting an application from MICO to omniORB.
>
> You should report it as a bug in MICO.

It depends. MICO's include/mico/except.h file contains following code:

enum completion_status {
    COMPLETED_YES,
    COMPLETED_NO,
    COMPLETED_MAYBE
};

typedef completion_status CompletionStatus;

So, if you use right CompletionStatus it'll work with MICO too. Maybe you
can accuse MICO of confusing users by user visible completion_status
type.

Cheers,

Karel
--
Karel Gardas                  kgardas@objectsecurity.com
ObjectSecurity Ltd.           http://www.objectsecurity.com