🚀 go-pugleaf

With the result of the function being a TObject, yes it is the same, its
just poor programming practice. Notice he mentioned scope. You normally do
not want to "hide" the creation of an object in such a manner, but there can
be reasons for it at times.

"BobRoyAce" <bob@omegasoftwareinc.com> wrote in message
news:3ddda7b1$1@newsgroups.borland.com...
> Wouldn't your solution just be the same as doing the following?
>
> var
>   MyObj: TObject;
> begin
>   MyObj := SomeProc(1);
>   MyObj.DoSomething;
>   MyObj.Free;
>   ...
> end;
>
> function SomeProc(AOption: Integer);
> begin
>   Result := TObject.Create(AOption);
> end;
>
>
> "Ray Marron" <marron+delphi@cableaz.com> wrote in message
> news:3ddd63d1$1@newsgroups.borland.com...
> > Dana Dill <dana@danadill.com> wrote in message
> > news:3ddd61dd$1@newsgroups.borland.com...
> > > Hi:
> > >
> > > I have a function that returns a class.  I would like the returned
> object
> > to
> > > be a copy and not a pointer to the passed object.  How can I do this?
> >
> > This is usually done with a var parameter rather than having the
function
> > return an object.  This way, the caller is responsible for the scope of
> the
> > variable.
> >
> > For example:
> >
> > var
> >   MyObj: TObject;
> > begin
> >   SomeProc(1, MyObj);
> >   MyObj.DoSomething;
> >   MyObj.Free;
> > ...
> > procedure SomeProc(AOption: Integer; var AnObj: TObject);
> > begin
> >   AnObj := TObject.Create(AOption);
> > end;
> >
> > --
> > Ray Marron
> >
> >
>
>