ROS callbacks' scope and objects' lifecycles

asked 2019-01-19 12:10:25 -0500

Hypomania
120 ●20 ●24 ●29

I am quite new to C++. I know that callbacks with return type of ConstPtr& are of boost::shared_ptr<const MsgType> type.

Now, when dealing with callbacks, does one copy or initialize objects by reference? For example, I have a ROS msg with fields int x and int y[]. Within the callback, would I copy x and y or initialize references for both of them?

Another thing, how can I know which objects are being copied and which ones are being referenced? Let's say msg->x and msg->y are they copied or referenced?

I am not familiar with object lifecycle and RAII at this point, could someone please explain to me in Layman's terms what's going on within ROS callbacks when ConstPtr& is used?

edit retag flag offensive close merge delete

add a comment

answered 2019-01-19 14:46:30 -0500

PeteBlackerThe3rd

flag of United Kingdom of Great Britain and Northern Ireland

9529 ●30 ●143 ●135 https://www.linkedin.c...

Just to clarify something, callbacks don't have a return value they are void. You may mean they accept a parameter of type ConstPtr&.

This parameter that is passed to the callback function is a reference to the actual message data stored by ROS message passing system. Creating references to this data is a bad idea since after the callback completes that data will probably stop existing so you'll have invalid pointers, bugs, segfaults and all the things we hate. For this reason your callback function should always make copies of data that you intend to use after the callback has finished.

Your other questions are more general C++ issues, but your question doesn't make any sense without the context of the code it's within. A direct copy, or pointer copy (reference) are always done with an assignment = statement, without an assignment statement we can't answer your question.

I would like to point out that C++ ROS is not a great place to be if you're new to C++. We use some very complex features of the language, I would recommend working through some dedicated C++ tutorials or courses outside of ROS to learn the language itself.

edit flag offensive delete link

Comments

Thank you again for your excellent answer. I understand that C++ ROS is complex, I am coming from embedded C background so I do know some C style concepts.

Hypomania ( 2019-01-20 04:23:23 -0500 )edit

As to my second question, all I want to know for now is when objects, within callbacks are, copied. I remember you telling me that copying a vector is as simple as doing msg->vec, however with arrays it was completely different, there is no simple arrow operator assignment, why?

Hypomania ( 2019-01-20 04:24:31 -0500 )edit

msg->vec doesn't copy anything. It's a statement which has the value of the vec member of a struct/class which is pointed to by a variable called msg. The -> operator isn't an assignment it simply refers to a member of structure identified by a pointer.

PeteBlackerThe3rd ( 2019-01-20 13:14:44 -0500 )edit

@PeteBlackerThe3rd, so I am assuming the way vec would be copied is by one of the operator overloads? I thought equating two vectors together is considered as a copy. msg->vec would mean you are equating a vector to another vector. For e.g.: = x = (*msg).vec, where vec and x are both vecs.

Hypomania ( 2019-01-21 13:59:47 -0500 )edit

You're right x=(*msg)->vec will copy the vector using the overloaded = operator. Similarly std::vector<type> *x = &(*msg)->vec; will copy a pointer to the vector. The first makes a copy of the data while the second makes a reference to the original.

PeteBlackerThe3rd ( 2019-01-21 16:00:41 -0500 )edit

@PeteBlackerThe3rd, crystal clear, thank you!

Hypomania ( 2019-01-24 10:30:02 -0500 )edit

add a comment

ROS callbacks' scope and objects' lifecycles

1 Answer

Comments

Question Tools

Stats

Related questions

ROS callbacks' scope and objects' lifecycles edit

1 Answer

Comments

Question Tools

Stats

Related questions

ROS callbacks' scope and objects' lifecycles