I am not critizing the teacher's choice of restrictions with respect to the problem at hand; I am questioning their worth as such.

Without knowing what the instructor's goals were with this assignment, I don't know how you can do that. What's a simple way of teaching someone inheritance? Or juggling a half-dozen different object types in an application? Or maybe methods for working with (identifying?) object types when said objects might be used interchangeably? This assignment could fit any of those. The original poster gave us his requirements, but never stated the goal of the exercise.

And if I were teaching an entry-level object-oriented programming course, I would not want to wade through 50 pages of someone's crappy code. I've had CS instructors say, "This probably shouldn't take more than X lines of code to do," but rarely was a size limit strictly imposed, I will agree with that. But I can also see how some instructors might want to do that. That's just a personal decision. This length requirement really doesn't surprise me.

But, alas, this is kind of getting off-topic. Yes, in the real world there are practical and design reasons you may or may not want to go with an OO design. But this isn't a real world: it's an exercise with an unknown goal. "Silly restrictions" should hardly be surprising.

In reply to Re: Re: Re: Re: OO 2 death? by Fastolfe
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.