[Rock-dev] adding boost::shared_pointer and boost::weak_pointer to rtt/rock?

[Matthias Goldhoorn]

On 09.09.2013 13:42, Sylvain Joyeux wrote:
> On 09/09/2013 01:03 PM, Matthias Goldhoorn wrote:
>> "Moin moin",
>>
>> What would be needed to add some of the boost shared_pointer structures
>> to rock/rtt?
>> special boost::shared_pointer and boost::weak_pointer?
> You most probably don't want to do that. boost::shared_pointer and
> boost::weak_pointer have bad multi-threading semantics.
maybe stuffing this into the smart_ptr for locking/unlocking?
>
> What do you actually want to achieve ?
>> How is the transport of the smart_ptr currently handled?, what happen if
>> the same object is send twice trough an RTT port over the boarders of a
>> application (or machine) (e.G. CORB//mqueues)?. Is there a tracking of
>> object identification/id? or will be the object simply represented twice
>> on the receiving machine?
> There are no tracking of object identification. If you send the same
> object twice, you'll get it twice.
That's What i thought already.
>
> Again, what is the actual situation / use case / problem you are trying
> to solve ?
The use case is a library which hardly uses these structures for 
internal handing (lists/vectors of 3D Point-cloud data).
Pointcloude -> segmentation -> feature extraction -> post processing 
(and in between often visualization).
The plan was to add rock between the -> for 
transport/replay/debugging/modularization. To be as compatible to the 
original library implementation it would be nice to have support for the 
mentioned data-structures.

>


-- 
  Dipl.-Inf. Matthias Goldhoorn
  Space and Underwater Robotic

  Universität Bremen
  FB 3 - Mathematik und Informatik
  AG Robotik
  Robert-Hooke-Straße 5
  28359 Bremen, Germany

  Tel.:     +49 421 178 45-4193
  Zentrale: +49 421 178 45-6550
  Fax:      +49 421 178 45-4150
  E-Mail:   matthias.goldhoorn at uni-bremen.de

  Weitere Informationen: http://www.informatik.uni-bremen.de/robotik