I couldn't figure out why my request class was giving me exceptions when I accessed it, until I found this line:

 fServerRequest := TServerRequest.Create;

When I changed it to:

 fServerRequest := TServerRequest.Create(nil);

Everything worked.

Shouldn't the compiler complain that I was missing a parameter?

Thanks,
Doug

Doug,

<< Shouldn't the compiler complain that I was missing a parameter? >>

TObject.Create

Tim Young
Elevate Software
www.elevatesoft.com

Tim Young [Elevate Software] wrote:

> << Shouldn't the compiler complain that I was missing a parameter? >>
>
> TObject.Create

Forgive me, but I don't understand that. I checked the help to see if
that was a pointer to something, but nothing obvious.

--

Matthew Jones

Matthew,

<< Forgive me, but I don't understand that. I checked the help to see if
that was a pointer to something, but nothing obvious. >>

He was calling the TObject.Create method, not the TComponent.Create method.
One must always remember that there's a public TObject.Create ancestor
method that will match a Create call without any parameters.  When that
happens, the TComponent.Create method isn't called, and all of the
ownership, parenting, etc. initialization that occurs normally will *not*
occur.

Tim Young
Elevate Software
www.elevatesoft.com

Tim Young [Elevate Software] wrote:

> << Forgive me, but I don't understand that. I checked the help to see
> if that was a pointer to something, but nothing obvious. >>
>
> He was calling the TObject.Create method, not the TComponent.Create
> method. One must always remember that there's a public TObject.Create
> ancestor method that will match a Create call without any parameters.
> When that happens, the TComponent.Create method isn't called, and all
> of the ownership, parenting, etc. initialization that occurs normally
> will not occur.

Ah, right. A sort of standard inheritance gotcha, that we don't usually
fall over, but just might.

--

Matthew Jones

Thanks, Tim.

I guess it's just different in Delphi, where the following would show an error:

" E2035 Not enough actual parameters"

var
 c: TComponent;
begin
 c := TComponent.Create;
end;

Doug

"Tim Young [Elevate Software]" wrote:

Matthew,

<< Forgive me, but I don't understand that. I checked the help to see if
that was a pointer to something, but nothing obvious. >>

He was calling the TObject.Create method, not the TComponent.Create method.
One must always remember that there's a public TObject.Create ancestor
method that will match a Create call without any parameters.  When that
happens, the TComponent.Create method isn't called, and all of the
ownership, parenting, etc. initialization that occurs normally will *not*
occur.

Tim Young
Elevate Software
www.elevatesoft.com

Doug,

<< I guess it's just different in Delphi, where the following would show an
error: >>

EWB's compiler has automatic overloads.  If it finds a method with the
correct signature *anywhere* in a given class hierarchy, then it will
consider it resolved and use it.

Tim Young
Elevate Software
www.elevatesoft.com