Not really - what I was doing was simple - formatting a week at a glance page. Stuff for each day comes in, HTML goes out. However, my teacher is schizoid on being able to easily modify code - he wouldn't let me have Monday and Tuesday be the same. I had to seperate those into seperate classes. I used inheritance as much as I could, but that was because he placed a 1.5 page limit (with comments and whitespace) on my modules. I couldn't cram a constructor, initializer and actual code into the module like I wanted to. I frequently use inheritance, but this case was so simple it was overkill - I didn't even need the most basic of OO tools to do this. Ridiculous thing is, while I'm taking this course I'm doing a coding co-op, and my employer openly encourages the simple solution - top->down, reuse, 3rd party stuff ... I've done much more complicated projects in less time than that dumb one.

So, no, there wasn't anything I could really do in that instance - OO was forced, to a negative end. I'm pretty sure it sucks more resources than it needs as well.

Cestus

Microsoft and Shinra are the same. They're both killing the planet.

In reply to Re: Re: OO 2 death? by Cestus
in thread OO 2 death? by Cestus

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.