Re: Interesting take on Paradigms (OO vs Procedural)



On Fri, 28 Mar 2008 12:08:44 -0500, "Rick Smith" <ricksmith@xxxxxxx>
wrote:

Why did the originators of object orientation rename "structures" to
"objects"
and "procedures" to "methods"? Hubris and arrogance, in my opinion. Some
people believe object orientation is a completely new "paradigm" for
programming. The best known paradigms for computer languages are these.

I believe it was to divorce their design from programming terms. Of
course, that didn't last.
.



Relevant Pages

  • Re: Interesting take on Paradigms (OO vs Procedural)
    ... Why did the originators of object orientation rename "structures" to ... people believe object orientation is a completely new "paradigm" for ... programming. ... The best known paradigms for computer languages are these. ...
    (comp.lang.cobol)
  • Interesting take on Paradigms (OO vs Procedural)
    ... Why did the originators of object orientation rename "structures" to ... people believe object orientation is a completely new "paradigm" for ... programming. ... The best known paradigms for computer languages are these. ...
    (comp.lang.cobol)
  • Re: LSP and subtype
    ... What is the class of problems solvable using UML? ... the language of physics cannot describe. ... whatever paradigm equivalent to 2GL/3GL ... there is still a great need for reuse and generic programming. ...
    (comp.object)
  • Re: OO Methodolgy Perspective
    ... on a methodology like XP (eXtreme Programming) or other Agile ... One of the problems with Structured Programming was that everything about the solution was expressed in computing space terms. ... One thing the OO paradigm brought to the table were a set of step stones to bridge that gap in a systematic way. ... But if the OOA/D has been done correctly, ...
    (comp.object)
  • Re: New paradigm of introspective OO development
    ... > of serious programming work experience, ... and less to talk of "new paradigm". ... Formalization is essential, imho, ... Ideas are always worth exploring - keep in mind that fixing ...
    (comp.object)