🚀 go-pugleaf

"Zoetjuh" <peter@i-hate-spam.zoetjuh.demon.nl> wrote in message
news:41e84d3b@newsgroups.borland.com...

> Check http://www.zoetjuh.demon.nl/isnull.jpg
> It's there... :(

It is simply not possible for the Connection to be NULL.  Look at the source
code for TIdThread and TIdPeerThread.  The Connection is assigned, then
OnExecute is called in a loop, then the Connection is freed.  There is
nothing that frees the Connection while OnExecute is still looping.  In
fact, it is not possible for OnExecute to be triggered with a NULL
Connection because the Connection object is used to trigger the OnExecute
event in the first place, so the Connection is always guaranteed to be
valid:

    procedure TIdPeerThread.Run;
    begin
        //...
        if not Connection.Server.DoExecute(Self) then begin // <-- non-NULL
Connection!!!
        //...
    end;

    function TIdTCPServer.DoExecute(AThread: TIdPeerThread): boolean;
    begin
        //...
        Result := Assigned(OnExecute);
        if Result then begin
            OnExecute(AThread); // <-- OnExecute triggered by accessing
non-NULL Connection!!!
        end;
        //...
    end;


Gambit