Re: Interesting take on Paradigms (OO vs Procedural)
- From: "Rick Smith" <ricksmith@xxxxxxx>
- Date: Sat, 29 Mar 2008 18:21:54 -0500
"Pete Dashwood" <dashwood@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:657mp4F2dooroU1@xxxxxxxxxxxxxxxxxxxxx
essential
"Rick Smith" <ricksmith@xxxxxxx> wrote in message
news:13ur5tg3con5ja4@xxxxxxxxxxxxxxxxxxxxx
"Pete Dashwood" <dashwood@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:65553nF2cjsrhU1@xxxxxxxxxxxxxxxxxxxxx
"Rick Smith" <ricksmith@xxxxxxx> wrote in message
news:13uq9i0e2sfdd1a@xxxxxxxxxxxxxxxxxxxxx
< http://www.cs.berkeley.edu/~jrs/4/lec/14 >
-----
Why did the originators of object orientation rename "structures" to
"objects"
and "procedures" to "methods"? Hubris and arrogance, in my opinion.
This simply says that the writer has not really understood the
betweendifferences. I read the full article and he/she does a good job ofthe
listing
the differences, but identifying differences and actually understanding
implications of those differences are two different things.
The comment above implies that the commentator sees no difference
thingsa
"structure" and an "object", yet anyone who has worked with these
completelyinYou are looking only at the mechanics of an implementation. The conceptual
the real world would understand the essential difference. This is the
difference between Acadaemia and Reality.
H'm! Structure, in procedural, is accessed through a pointer.
Object, in object-based, is accessed through a reference.
Object, in object-oriented, is accessed through a reference;
but also holds a "vtable" to accommodate inheritance and
polymorphism.
The essential difference seems to be the extension of the
structure to add the "vtable" making the object a bigger
structure.
use of objects is WAY more important. But you only come to appreciate that
when you start using them for systems in the real world, and not just to
describe some academic argument.
Whether objects implement inheritance through a vtable or not is
irrelevant to the use of objects. For you, an object is just a structurein
memory; for me, it is much more than that. I visualise objects asa
representing a real world entity and having attributes and behaviours that
structure alone can never have. Perhaps it comes down to imagination and
vision.
I used to see objects as real world entities. Now I associate
real world entites with classes, because the methods in the
classes repesent behavior. If one is to "simulate" anything,
it is the behavior that is to be simulated.
To simulate a business, the behavior occurs in employees,
customers, orders, accounts, etc.; but to simulate the
financial systems of a business the behavior is in clerks, and
the employees, customers, orders, accounts, etc., become
just data structures devoid of behavior. This is not much
different than a card game, where the dealer and players
have behavior but the cards don't; even though the cards
are real world entities.
.
- References:
- Interesting take on Paradigms (OO vs Procedural)
- From: Rick Smith
- Re: Interesting take on Paradigms (OO vs Procedural)
- From: Pete Dashwood
- Re: Interesting take on Paradigms (OO vs Procedural)
- From: Rick Smith
- Re: Interesting take on Paradigms (OO vs Procedural)
- From: Pete Dashwood
- Interesting take on Paradigms (OO vs Procedural)
- Prev by Date: Re: Interesting take on Paradigms (OO vs Procedural)
- Next by Date: Re: Interesting take on Paradigms (OO vs Procedural)
- Previous by thread: Re: Interesting take on Paradigms (OO vs Procedural)
- Next by thread: Re: Interesting take on Paradigms (OO vs Procedural)
- Index(es):
Relevant Pages
|