Jim Dettman
jimdettman at verizon.net
Sun Jan 7 06:02:29 CST 2007
John, <<Write once, use forever, you applications become consistent throughout (and EXTREMELY powerful). But it is not the application providing the power, it is your framework.>> Yeah it sounds good, but you haven't told them about the problem with composite classes<g>. This is where OOP just falls flat on it's face. After programming with VFP for a few years, I realized I basically had the same problems as before except that things were a heck of a lot more complex to figure out. Up to that point, I had developed methods (calling standard procedures and changing code on the fly) to work in non-OOP languages that gave me the ability to do things like you are discussing. The promise of OOP is that you define it once and it works everywhere. But when you start getting into composite classes, you find once again that you have the same code in a lot of different places and are almost back to square one. Also with OOP you spend a lot of time figuring out the state of things because you don't know what other routines may have done. Since your not supposed to look inside the box, you can never be sure of anything when your within an object. It also requires heavy time up front to properly develop your classes and interfaces and the class hierarchy. Screw up with those and you'll be rewriting a lot. OOP does have it's place and it can be powerful and flexible, but you need to go into it with your eyes open. It's not the pancrea for programming problems that everyone believes. Think about how long OOP has been around; why is there not more of it? If it was really that great it should have flooded the development community by now, yet here we are almost 30 years later still using non-OOP languages. I think there is nothing wrong with using objects simply as a means of simplifying data structures, but using an object orientated language is not all it's cracked up to be. Jim. -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of JWColby Sent: Saturday, January 06, 2007 11:39 PM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] Log Class part 1B Yes! Maybe. If you are talking about a callback function then the answer is "damned tough". However for objects like forms and controls.... <<snip>>