Sujet : Re: What is OOP?
De : tr.17687 (at) *nospam* z991.linuxsc.com (Tim Rentsch)
Groupes : comp.lang.c++Date : 29. Mar 2025, 21:33:53
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <86ecyfinke.fsf@linuxsc.com>
References : 1 2 3 4 5
User-Agent : Gnus/5.11 (Gnus v5.11) Emacs/22.4 (gnu/linux)
Michael S <
already5chosen@yahoo.com> writes:
On Mon, 17 Mar 2025 10:17:51 -0700
Tim Rentsch <tr.17687@z991.linuxsc.com> wrote:
>
The late binding that Alan is talking about is the binding of
messages to processing activity. Note the contrast with calling
a function, where the binding of name to what processing is done
is static rather than deferred.
>
It sounds like very flexible paradigm that I very certainly don't want
to use.
I like majority of my mistakes caught in compile/link/load time rather
than in run time.
It's important to understand that object-oriented programming is
more about mindset than it is about any particular set of language
features. In particular, OOP is not incompatible with strong type
checking, especially under the "majority" criterion. There are
languages with classes and inheritance that also impose strict type
checking (OCaml is one example), which I think would get you the
property you want of catching most mistakes before run time. I
don't mean to suggest that a combination "ideal OOP" and perfect
type checking is a solved problem, it isn't. My sense though is
that languages that are available now can supply between 80 and 90
percent of both. You might want to try looking into whether that
could do what you want.