On 7/20/07, Adam Perry <[EMAIL PROTECTED]> wrote:
> I... don't think that's the purpose of pointers.
What? A pointer shunts responsibility for a chunk of memory from the
callee to the caller (or, vice versa, for a return value). This
implies, strongly, that the callee will be modifying the content
On Fri, Jul 20, 2007 at 05:00:33PM -0500, Mike Caron wrote:
> On 7/20/07, James Paige <[EMAIL PROTECTED]> wrote:
> > Hey, Mike. I noticed that DeSerHeroDef and SerHeroDef expect a herodef
> > ptr rather than just taking a herodef as an argument. Why is this? If
> > the herodef object was passed by
I... don't think that's the purpose of pointers.
On 7/20/07, Mike Caron <[EMAIL PROTECTED]> wrote:
On 7/20/07, James Paige <[EMAIL PROTECTED]> wrote:
> Hey, Mike. I noticed that DeSerHeroDef and SerHeroDef expect a herodef
> ptr rather than just taking a herodef as an argument. Why is this? If
On 7/20/07, James Paige <[EMAIL PROTECTED]> wrote:
> Hey, Mike. I noticed that DeSerHeroDef and SerHeroDef expect a herodef
> ptr rather than just taking a herodef as an argument. Why is this? If
> the herodef object was passed by value (copied) I would understand the
> need for using pointers, but
Hey, Mike. I noticed that DeSerHeroDef and SerHeroDef expect a herodef
ptr rather than just taking a herodef as an argument. Why is this? If
the herodef object was passed by value (copied) I would understand the
need for using pointers, but I was under the impression that objects are
passed by
