Is his code buggy or a maintenance disaster waiting to happen? If so then you have a point and an argument. Analyse his code, identify a feature that will require him to rewrite the whole thing but that could be implemented easily in an OO framework. Then ask him to make the change. Point out afterwards how much easier it would have been.

If his code isn't ugly and works, and the thing that is really bothering you is that he wont admire your cool shiny OO framework, then I advise that you get over it. Only if you can really put your finger on things that have gone wrong due to his programming style will you be able to win an argument, and even then it will be a hard battle.

---
$world=~s/war/peace/g

In reply to Re: Coding styles: OOP vs. Subs by demerphq
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.