Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider removing mapping_ and getMapping() from PointCloud #2506

Closed
taketwo opened this issue Oct 1, 2018 · 6 comments
Closed

Consider removing mapping_ and getMapping() from PointCloud #2506

taketwo opened this issue Oct 1, 2018 · 6 comments
Assignees
Labels
Milestone

Comments

@taketwo
Copy link
Member

taketwo commented Oct 1, 2018

It seems that mapping_ is used only by

namespace detail
{
template <typename PointT> boost::shared_ptr<pcl::MsgFieldMap>&
getMapping (pcl::PointCloud<PointT>& p)
{
return (p.mapping_);
}
} // namespace detail

But getMapping() is never used in the project, so mapping_ does not need to be swapped.

PS: mapping_ and getMapping() might be removed from the project.

Originally posted by @csukuangfj in #2470 (comment)

@SergioRAgostinho
Copy link
Member

👍 it seems to be there since the first commit a024ad2 and nothing was using it back then.

@taketwo
Copy link
Member Author

taketwo commented Oct 7, 2018

Also consider moving detail::FieldMapping and MsgFieldMap to "conversions.h", because this is the only place they are used.

@taketwo taketwo self-assigned this Oct 7, 2018
@stale
Copy link

stale bot commented May 19, 2020

Marking this as stale due to 30 days of inactivity. It will be closed in 7 days if no further activity occurs.

@stale stale bot added the status: stale label May 19, 2020
@kunaltyagi kunaltyagi added this to the pcl-1.12.0 milestone May 20, 2020
@stale stale bot removed the status: stale label May 20, 2020
@kunaltyagi kunaltyagi added the kind: todo Type of issue label May 20, 2020
@larshg
Copy link
Contributor

larshg commented Nov 30, 2020

This one can be closed?

@kunaltyagi
Copy link
Member

I think so. 1.12 will take care of actually removing the variable

@larshg
Copy link
Contributor

larshg commented Nov 30, 2020

Yeah, its removed in #4341.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants