Re: Inherited explained
- From: Jamie <jamie_ka1lpa_not_valid_after_ka1lpa_@xxxxxxxxxxx>
- Date: Tue, 21 Oct 2008 18:07:45 -0400
Anonymous Remailer wrote:
With all due respect, your knowledge into delphi/pascal has created a completely incoherent explanation. This is why I have not been able to completely comprehend the inherited statement before.If you understand Linked List... Just think of a list of pointers
I will protest this line, however: 'This suggests to me that you have a very ad-hoc and antagonistic understanding of how to build a system of cooperating classes.'
To go into slandering someone's character in your explanation is patently wrong.
all pointing to class methods and your newly overridden class procedure
simply added it self to the top of the list.. The "inherited" points to
the procedure just before yours. And that procedure will then have it's
inherited pointer that points to the procedure before that one and so on.
The one on top gets it first as in all cases of nature!//
Maybe that explanation will be clearer to you.
there is a little more processing going on in the background but I
think you get the idea.
http://webpages.charter.net/jamie_5";
.
- References:
- Re: Inherited explained
- From: Maarten Wiltink
- Re: Inherited explained
- From: Anonymous Remailer
- Re: Inherited explained
- Prev by Date: Re: Delphi language support in CMake build system
- Next by Date: Re: Inherited explained
- Previous by thread: Re: Inherited explained
- Next by thread: Revised: Re: Inherited explained
- Index(es):
Relevant Pages
|
