Re: OOP - a question about database access
Date: Tue, 18 Nov 2003 17:13:16 -0500
Message-ID: <b8342$3fba997d$3f47e403$23754_at_msgid.meganewsservers.com>
"Joe "Nuke Me Xemu" Foster" <joe_at_bftsi0.UUCP> wrote in message
news:1069192553.397978_at_news-1.nethere.net...
> "Uncle Bob (Robert C. Martin)" <u.n.c.l.e.b.o.b_at_objectmentor.com>
wrote in message
> <news:0kejrv44sor2vot6op4d4fk9c4ueppv9fn_at_4ax.com>...
>
> > "Joe \"Nuke Me Xemu\" Foster" <joe_at_bftsi0.UUCP> might (or might not)
> > have written this on (or about) Mon, 17 Nov 2003 19:09:33 -0800, :
> >
> > >"Uncle Bob (Robert C. Martin)" <u.n.c.l.e.b.o.b_at_objectmentor.com>
wrote in message
> > ><news:nucirv8q2j2horrto5i6dtrmpi5smhsdtc_at_4ax.com>...
>
> > >> No, there are those of us who think that polymorphism is even
more
> > >> important than encapsulation.
> > >
> > >Which kind of polymorphism? Static or dynamic, interfaces or
> > >code inheritance, Third Manifesto or non-circular circle, etc.?
> >
> > Dynamic polymorphism.
>
> Everyone seems to have a different definition for this term.
"Dynamic"<=>"Static"
in our industry for decades denotes
static - compile time event dynamic - run-time event
Some of us equate:
` templates, or generics
` method name overloading
as major static forms of polymorphism
The usual swap object cum its method implementations during run-time most in OO consider as a major form of dynamic polymorphism.
Indeed these
Elliott
` objects/classes are the core/key granule of abstraction, and
` objects/classes collaborate in networks of relationships and
` as a result manifest or make profound abstraction, polymorphism,
identity, encapsulation, state, [metamorphism, aspects]
are the fundamentals of the OO modelling paradigm
--
Be bold, be artistically imaginative, yet scientifically grounded -- DO
GREAT OO MODELLING WITH OBJECTS OF ALL TYPES!!
--
*~* Theory Leads, Practice Verifies *~*
*~* Global Plans + IID (Iterative & Incremental Development) *~*
Received on Tue Nov 18 2003 - 23:13:16 CET