🚀 go-pugleaf

"Taligent's Guide to Designing Programs" (Addison Wesley, 1994) has
some things to say about this.  Taligent recommends a naming convention
for C++ functions that can be summarized as follows:

Create... for functions that make a new object that the caller must
  delete.

Copy... for functions that copy an existing object that the caller
  must delete.

Orphan... for functions that pass deletion responsibility to the caller.

Adopt... for functions that assume responsibility for deleting objects
  that have been allocated by the caller.

This convention can be extended for argument names; e.g., a constructor
for an objects that takes on ownership of the arguments:

  AndNode::AndNode(Node* adoptedLeftChild, Node* adoptedRightChild)

IMHO, object ownership is not a big deal if you conciously design for it,
and use conventions like those above to help document the decisions.
---
[ comp.std.c++ is moderated.  Submission address: std-c++@ncar.ucar.edu.
  Contact address: std-c++-request@ncar.ucar.edu.  The moderation policy
  is summarized in http://dogbert.lbl.gov/~matt/std-c++/policy.html. ]