--- Dan Muey <[EMAIL PROTECTED]> wrote: > A noble task indeed! > I don't know of any links right off but here's a couple shorties : > - easier for other people to maintain even years from now > - easier to migrate and expand > - objects make it easier to interface and work with other things, > consistantly and without much effort > - decrease cost( time, money, space, prcessing power )
Agreed, agreed, agreed, agreed, and agreed, but they don't take my word for it. I need a way to prove it. :o/ > - increase efficiency and effectivity ( if something is running > inefficiently and therefore, say , slow a customer can be frustrated > and you lose a customer ) That one I'm not so sure about. Many times the object has MUCH more overhead that a custom-code solution, and the package-space lookups add a lot, too. Machine time isn't really an issue here, tho; programmer time is more valuable, and I *know* object code maximizes that.... I just can't get them to look past "that arrow stuff". ~sigh~ (And these are intelligent, competent programmers, too. How can they not see that sometimes a learning curve is a worthwhile investment?) Paul __________________________________________________ Do you Yahoo!? Yahoo! Tax Center - forms, calculators, tips, more http://taxes.yahoo.com/ -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
