>>Actually, I agree with you, but I'd like to play devil's advocate. What about those that say that OO is a tool just as everything else. It is to be used, but it is not an End-all, Be-all. There are some problems that don't lend themselves easily to an OO solution. In some rare occasions a PRG would actually be more effective.
>
>Dan --
>
>This is a very old argument...it was used way back in "the old days" as a reason not to adopt the tenets of structured design and programming. When someone states that "There are some problems that don't lend themselves easily to an OO solution," my usual response is, "Name one."
>
>Bill

Ok. Work with me on this one. I've got a particular method that I know that is going to need tweaking at the client site. Unfortunately the only way that the client we'll be able to communicate what he wants is by seeing the complete exe in concert with this particular method. For some reason I can't meed with the client ( lets say he lives on Mars ). So I have the method call a prg. I exclude the prg and send up the Exe and prg together. Now we talk over the phone and I have the ability to make changes on the prg as we're speaking and my client is very impressed. He thinks it magic or maybe some rare form of psychic ability.

I know this is a very specific area, but I'd like to know what are the Pros and Cons with this idea. This seems to me be violating some basic tenants of program theory but I can't pu my finger on it. Can something like this be achieved without using a prg ( or a table with a memo and code block ).