|
> this is a quite questionable statement. I dont want to miss > specialisation of real world objects by the use of inheritance. > I can easily demonstrate 100 places where this makes sense, its starts > in the range of persistence... Please demonstrate a few. And persistence is not an application requirement, it's an architectural issue. Name places in business applications where inheritance works better than composition. > But there are many oppinions about that. Think of one fact, no modern > language comes without inheritance. > The last 5-6 languages created the last years in fact are all completely > OO based. (Python, C#, Ruby, Java,...) None of those languages is any good for business logic, though. Also, your statement depends on what you consider a language. ILE RPG is all but a completely new language, and it does not have inheritance. And in any case, the point is not whether inheritance is good or bad, but whether it is appropriate for business programming. My position is that it is not, and that except for the most trivial applications I can write business logic much more quickly and flexibly in RPG than any other language. Joe
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.