------------------------------------------------ On Fri, 7 Mar 2003 07:56:29 -0800 (PST), Paul <[EMAIL PROTECTED]> wrote:
> > --- 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/ > Hindsight is 20/20 and about the only way to "prove" it. Isn't the sheer number of people doing it a good enough reason to at least examine its abilities? > > - 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?) > I would question whether they really are "intelligent, competent" programmers if they are discarding OOP because of the learning curve, rather than because it is overkill, etc. for the project. I am not going to run around waving my arms and shouting that OOP is always required for any successful project, I wouldn't be a very good Perl programmer if I did (IMHO), but to adequately judge which approach to take both need to be understood and it doesn't sound like they are, but I am also making the assumption that you are correct and that the project *does* warrant the OOP approach, and that the project warrants it above and beyond the learning curve. p.s. I am fighting the same battle, though I think I may have won. Our team is divided between 2 people who know Perl's real abilities and particular OOP methodology, and 2 that are new to Perl and OOP but are long time procedural programmers in other languages. And finally a team leader that really has neither, but she does have one thing, she recognizes who has the experience for this particular project and is listening...fingers crossed for you and I :-).... -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
