Re: [orbitcpp-list] Re: orbitcpp status and question

[Brian M. <ba...@sn...>]

>>>>> "John" == John Luebs <jk...@lu...> writes:

    John> Alot is still not completed, but most of the POA stuff
    John> is. The example you cite shows that the orbitcpp you are
    John> using is older than God, I think a lot of this stuff is in
    John> the latest release. And if it isn't then it certainly is in

No, this is the latest release, 0.29, from sourceforge. Of course, I
heard something about 0.30, but I don't think that is released yet.

Just do "grep NYI *.cc" shows a number of instances in one of the
source files:

orbitcpp_poa.cc:	error("NYI");
orbitcpp_poa.cc:	error("NYI");
orbitcpp_poa.cc:	error("NYI");
orbitcpp_poa.cc:	error("NYI");
orbitcpp_poa.cc:	error("NYI");

those functions are activate_object_with_id, deactivate_object,
reference_to_servant, reference_to_id, id_to_servant, destroy.

If 0.29 isn't the newest release, then obviously I am looking at web
pages that are incorrect. In this case, where can I get the latest
version from?

Where can I find up-to-date instructions on obtaining the CVS version?
(ie. hostname, directory, and login details).

    John> CVS. Of couse you also need to have a very late dev snapshot
    John> (or CVS) of ORBit to use bleeding edge orbitcpp. Also do not
    John> install this stuff in /usr or you will be sorry because
    John> precompiled versions of GNOME depend on release ORBit, and
    John> will die with the latest dev ORBit.

Hmmm. My current version of ORBit (0.5.5) seems OK at present.  I will
upgrade though if I encounter problems.

    John> The goal of this project is to faithfully implement the
    John> CORBA C++ mapping.  In the binding spec, deep copying is
    John> done sequences and arrays, and orbitcpp tries to follow the
    John> spec.  Now if you (or anyone) finds places where compliant
    John> code crashes due to a buggy copy (shallow where it should be
    John> deep), please contact the list.

Ok, thanks for the information. If I have any problems, I will
post them here.

On the topic of the specs, I was wondering, how do I free object
references?  I had a quick glance through the specs (probably should
check to ensure it is up-to-date: filename 99-07-41.pdf), but couldn't
find anything.

Currently I have:

  void destroy() {
    PortableServer::ObjectId *objid = poa->servant_to_id(this);
    poa->deactivate_object(*objid);
    CORBA_free(objid);
    delete(this);
  }

but not really sure if I have freed objid the correct way (isn't there
a C++ version of CORBA_free?)
-- 
Brian May <ba...@sn...>