Re: OOB or procedural
From: Gerry Quinn (gerryq_at_indigo.ie)
Date: 12/01/03
- Next message: goose: "Re: Programmer's unpaid overtime."
- Previous message: goose: "Re: Programmer's unpaid overtime."
- Next in thread: goose: "Re: OOB or procedural"
- Maybe reply: goose: "Re: OOB or procedural"
- Reply: Phlip: "Re: OOB or procedural"
- Maybe reply: Richard Heathfield: "Re: OOB or procedural"
- Maybe reply: Programmer Dude: "Re: OOB or procedural"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Mon, 01 Dec 2003 11:57:43 GMT
In article <gc9yb.32420$OP.30090@newssvr32.news.prodigy.com>, "Phlip" <phlip_cpp@yahoo.com> wrote:
>Gerry Quinn wrote:
>
>> >The pre-ANSI C compilers for AmigaOS support your OO definition. And
>> >AmigaOS itself is an excellent OS that supported extremely
>> >object-oriented windows, gadgets, blitter objects, etc.
>>
>> C is not an OO language and it does not support my definition of an OO
>> language. (I have no disagreement with the idea that OO concepts can
>> inform programming in non-OO languages.)
>
>If that breed of non-Standard C supported a kind of inheritance, and if you
>define OO as inheritance, then saying it's not OO because it's C is empty
>dogma.
But you referred to an OS that supported it, not a dialect of C.
Language features are not defined by those of the APIs they can access,
or the code that is written in them!
>Of course Standard C doesn't have inheritance!
>
>MS Windows's SendMessage architecture takes this only one step further.
>Applications register pointers to functions with each Window object
>(including the little Control Window objects embedded in top-level windows).
>Then the system dispatches messages to individual windows, and these route
>individual events in a big switch-case block. Modern wrappers hide this
>inside the MESSAGE_HANDLER() macros, but it's still the exact same thing.
>
>These systems use C to explicitely create the same virtual dispatch system -
>function pointers and switch-case blocks - that OO languages implicitely
>provide. But making those systems much lighter-weight allows one to use them
>much more strategically. The engineering expense of using them goes way
>down; they become a viable alternative to individual 'if' statements.
We all agree that one can implement OO ideas in non-OO languages. I
don't know what you mean by making them lightweight, though. I doubt
there are major differences in speed between the implementations.
Gerry Quinn
-- http://bindweed.com Screensavers and Games for Windows Download free trial versions New arcade-puzzler just out - "Volcano"
- Next message: goose: "Re: Programmer's unpaid overtime."
- Previous message: goose: "Re: Programmer's unpaid overtime."
- Next in thread: goose: "Re: OOB or procedural"
- Maybe reply: goose: "Re: OOB or procedural"
- Reply: Phlip: "Re: OOB or procedural"
- Maybe reply: Richard Heathfield: "Re: OOB or procedural"
- Maybe reply: Programmer Dude: "Re: OOB or procedural"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|