> --- 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/
That's why I put my email example in there, show them that. > > > - 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.... Not really, most modules make it basically transparent. Did you look at my email parsing example? It took me weeks to write and test and debug and on and on the origal. That four line beuty took me about half hour of reading cpan, trying it locally, then posting to this list for one Little thing I couldn't get, but actaully that had to do with something later in the script so never mind. > > I just can't get them to look past "that arrow stuff". ~sigh~ Big sigh on that. Ask them why they don't get rid of their blood when they're sick to release the evil spirits making them sick? Can they not get past "that science stuff"? Or moving on from tricycle to two wheel bike, can they not get past the "missing third wheel". ;p I'm sure they're great people but I'd hate to be you trying to persuade them That they'll end up spending more time doing "the confortable" way than the object way. I can say form experience that the first time you start with object and modules is a little weird but once you get it POW you can do all kinds of things quickly ans efficiently and the object way becomes the "comfortable way". I'm sure others would agree that it was the samw with them too. And heck it's not like I understand everything about objects either, you can find all kinds of posts form me asking for help on stuff about objects. That's how we learn and that same support will be there for them if they want it. Use the email example, see if they can look at it and figure out what it's doing. That should illustrate the object vs. weeks to develop/hundreds of lines/not taking inot account evry aspect os RFC standards version. Have them image having to write it, could they save time? Have them image having it handed to them to "parse the 'text/plain' mime type out of it". If they look at cpan to see what tidy_body() did then they'd see that @body contains the mimed up body of the message. So that's what they'd mess with. Use that as an illustration and learning tool, others here may offer similar illustrations if you ask nicely ( which you already have ) DMuey > (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]
