问题描述
几个月前,我创建了一个标题为What is / is not
被认为是优秀的OO编程的帖子。这开始了很长的讨论。
我把论点浓缩成一篇文章,可以是
查看
我完全相信这是另一场火焰战争的开始,所以锐化
你的刀子被卡住了!
Tony(你这样做,我会做得更好)Marston
Several months ago I started a thread with the title "What is/is not
considered to be good OO programming" which started a long and
interesting discussion.
I have condensed the arguments into a single article which can be
viewed at
http://www.tonymarston.net/php-mysql/good-bad-oop.html
I fully expect this to be the start of another flame war, so sharpen
your knives and get stuck in!
Tony (you do it your way and I''ll do it better) Marston
http://www.tonymarston.net/
推荐答案
太棒了。我会在假期后阅读它,如果你不介意的话,可以通过电子邮件联系
。
Jochen
-
Jochen Daum - CANS Ltd.
PHP DB编辑工具包 - 用于构建的PHP脚本
数据库编辑界面。
嘿,这是一份写得很好(或放在一起)的文件。我会保证这是好的用途。
Hey that''s a really well written (or put together) document. I''ll be
saving that for good use.
我觉得你还是不明白对象的构成很有趣。
在您的文章中,您写道:如何在OO系统中共享代码?通过
继承。,甚至没有提到对象组成。对象组成
也是我论证的关键,即:你只看到继承,我看到继承和组合。由此我们只能推断出你在
中的事实并没有正确理解我的论点。这并没有使
讨论变得更容易。
然而,OOP中的大多数初学者都面临着这个特殊的问题,他们是
过度使用继承,因为这通常是他们学习的第一件事,而且一旦他们掌握了它,他们就不会放手。
$ b $bAndrén?ss
I just think it''s funny that you still don''t understand object composition.
In your article you write: "How do you share code in OO systems? Through
inheritance.", not even mentioning object composition. Object composition
was also the crux of my argument, i.e.: where you see only inheritance, I
see inheritance and composition. From this we can only deduce that you in
fact did not properly understand my argument. That doesn''t make the
discussion any easier.
But then again, most beginners in OOP face this particular problem, they
overuse inheritance because that''s usually the first thing they learn, and
once they get the hang of it, they won''t let go.
André n?ss
这篇关于什么是/不被认为是良好的OO编程的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!