Linked by Thom Holwerda on Sat 26th Nov 2005 17:02 UTC, submitted by Megatux
Thread beginning with comment 65542
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 06/20/13 6:17 UTC, submitted by MOS6510
Linked by Thom Holwerda on 06/19/13 23:02 UTC, submitted by M.Onty
Linked by Thom Holwerda on 06/19/13 22:28 UTC
Linked by Thom Holwerda on 06/18/13 22:33 UTC
Linked by Anonymous on 06/18/13 22:26 UTC
Linked by Thom Holwerda on 06/18/13 22:25 UTC
Linked by Thom Holwerda on 06/18/13 17:45 UTC
Linked by Thom Holwerda on 06/18/13 17:32 UTC, submitted by poundsmack
Linked by Thom Holwerda on 06/17/13 17:58 UTC
Linked by Thom Holwerda on 06/17/13 17:52 UTC
More News »
Sponsored Links



Member since:
2005-10-19
ma_d, you said: "Very few people need to work on a library, as compared to how many will use it."
True, and that's another area where Eiffel excels. Eiffel code adheres to the open-closed principle. Eiffel programmers do not believe that once you write a library, people are only willing to use it, not change it. There's no such distinction between use and change except when it is forced upon one like C libraries do.
In Eiffel it's easy to inherit parts of a library and extend it. And it won't break any code because of Eiffel's DbC support: the invariant of a class must be maintained, even if you extend that class and change some features. Allows for very safe reuse.