A
agent_008_nl
Guest
Peter, My previous reaction has not been put on the forum for to me unknown reasons. Moderator? I had a short look at www.pugchallenge.eu/.../progress---advanced_ooabl_patterns.pdf since I'm doing a massive refactoring job ( > 9 months fulltime work) on an openedge oo backend. I find a least a part of the recommendations examples of bad practice. For example "Use inheritance for common or shared behaviour". Part of my refactoring consist of removing inheritance / subtype polymorphism from the application I'm working on. I sent messages before about it: community.progress.com/.../34837 , there are more threads where I said something about it. Even the GOF book says " favor composition over inheritance". Gus has criticism also, I would love him to write a couple of sentences on the subject. But in the meantime you could ask him when you're interested. About your other advises I would recommend to look for criticism on the internet and think it all out before adding needless complexity which will be regretted lateron when maintenance is necessary. I have a hell of a job removing needless complexity / "recommended practices" now.
Continue reading...
Continue reading...