Re: Anti-OO article appears to have plagiarized bits of my site
From: topmind (topmind_at_technologist.com)
Date: 01/28/05
- Next message: Dmitry A. Kazakov: "Re: Liskov Substitution Principle and Abstract Factories"
- Previous message: topmind: "Re: Anti-OO article appears to have plagiarized bits of my site"
- In reply to: stevenwurster_at_lycos.com: "Re: Anti-OO article appears to have plagiarized bits of my site"
- Next in thread: topmind: "Re: Anti-OO article appears to have plagiarized bits of my site"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 28 Jan 2005 13:33:47 -0800
> Get and IDE that lets you manage this. Don't have
> one? Get one! Your language doesn't support that?
> Get a better language. Don't blame OO
> technology when programmers make mistakes.
> It's not the technology, it's the programmer. Well,
> except when the technology is C++, Java, or
> C#, that is. :-)
But one can say that about ANY code management problem: "If you had an
IDE that handled that, it wouldn't be a problem". Copy-and-Paste could
even be justified by that because an IDE hypethetically could allow one
make the same alteration to multiple copies of something. You may be
mistaking a bandaid for a solution.
> Encapsulation is NOT hiding things from other
> programmers. That is
> information hiding. Encapsulation is simply putting
> many things into
> one package, with the idea in the object-oriented
> world that these
> things go together in some logical way. I wish
> people would stop confusing this issue.
Nobody agrees on what encapsulation is. Besides, modules can also group
"related" functions. Further "related" tends to be more complicated
than it first seems. Often there are multiple orthogonal grouping
candidates such that one cannot group by all of them at the same time
in linear text.
For example, class A may have a "deleteA" method and class B may have a
"deleteB" method. Deletion is related, and one could argue that all
deletion methods should "go together" so that their implementations can
be more easily compared and contrasted, for example to study
refactoring options.
(I had problems posting this, so please forgive me if it ends up
twice.)
-T-
- Next message: Dmitry A. Kazakov: "Re: Liskov Substitution Principle and Abstract Factories"
- Previous message: topmind: "Re: Anti-OO article appears to have plagiarized bits of my site"
- In reply to: stevenwurster_at_lycos.com: "Re: Anti-OO article appears to have plagiarized bits of my site"
- Next in thread: topmind: "Re: Anti-OO article appears to have plagiarized bits of my site"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|