Probably because it is automatic in C++(?)
Regards,
SZ
On Tue, Feb 1, 2011 at 5:53 PM, Anton S. wrote:
> Tobias, oh, thanks a lot! Today is the day when I use to forget to call
> ancestors' methods :)
>
> --
> Anton
> --
> To unsubscribe or change your settings for TWSocket mailing list
> plea
Tobias, oh, thanks a lot! Today is the day when I use to forget to call
ancestors' methods :)
--
Anton
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be
Hello Anton!
> destructor TSrvClient.Destroy;
> begin
> FreeAndNil(FList); // *** set breakpoint here to ensure client is destroyed
> ***
> end;
This should be:
destructor TSrvClient.Destroy;
begin
FreeAndNil(FList);
inherited; // <-- added call to ancestor
end;
Regards,
Tobias
--
To
I faced strange issue when connected clients seem not to be removed from
server's list on disconnect.
I wrote simple demo project to test this, it'll be later. In short words,
client objects seem to never be deleted from FClientList. I've set breakpoint
on the line "FClientList.Remove(AComponent
