Coding style using shared_ptr

Aptitude Testing Team aptitude at
Wed Jun 1 07:33:35 UTC 2016

We have an inconsistency with the coding style in our shared_ptr typedefs

cd core/include; grep -R "typedef std::shared_ptr"

Shows (for "std::shared_ptr<Foo>") we have "FooPtr" or "FooRef" or "PFoo"

Should we standardise this?

FooPtr is my preference.

In addition we also have 3 typedef's for unique_ptr's. In my opinion, I
think these should be removed to avoid confusion

Any thoughts?

More information about the LibreOffice mailing list