>> Other than for code re-use, I still don't quite understand why OO is being forced onto a concept that is inherently procedural.
Forced is a strong word, but probably accurate given the current environment in development today. As people have said, there are situations where it is useful and others where it is most likely overkill. A good example of overkill is when developing a Mom & Pop, Inc. web site to sell watermelon lollipops, or a simple content management system for a small business. However, any major web application of significant complexity (valuate that however you will) should be using OO concepts in some degree. My current assignment has me looking over procedural code that was poorly written in 2000 as bad developers were put into a bad situation. Fast forward to 2004 and this code is now a momumental challenge to maintain and extend. Most modules easily reach 300-500 lines of code (sometimes more) and can accomplish several tasks. Tracking down one bug, even for highly skilled developers, can take an entire workday. It would require 8-12 months for a team of 3 or more developers to repurpose this into a manageable and scalable application. As we have heard, examples like this abound (which I still find amazing these days), and the best thing to focus on is writing clean, simple code that is adequately documented and follows industry best practices. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Special thanks to the CF Community Suite Silver Sponsor - CFDynamics http://www.cfdynamics.com Message: http://www.houseoffusion.com/lists.cfm/link=i:4:185676 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
