If I knew how to make co-workers do things my way, I'd probably be the CEO of some large company. This is a people problem.

Since you asked, there are some simple reasons why OO is usually better. You get more code reuse, more encapsulation of components, and thus code that withstands changes more easilly. A really good programmer can do this without traditional OO through careful design and some use of callbacks and such, but this guy does not sound that good.

What he's doing with the huge long files of code should not be tolerated. Splitting code into modules is not an OO thing; it's just a basic good practice.

Unfortunately, the fact that he sees no problem with writing these huge files probably means he isn't very interested in writing good code. Even if you do convince him to use OO, he will probably not know how to do it effectively, and will just write enormous class files.

Finally, claiming performance as a reason not to use OO is absurd. Are you writing some kind of 3D shooter in perl? Has he profiled the code and discovered that method calls are slowing you down? I didn't think so. Your bottleneck is probably I/O (database, disk) like it is for almost every other program written in perl.

In reply to Re: Coding styles: OOP vs. Subs by perrin
in thread Coding styles: OOP vs. Subs by nikos

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.