comment on

I started out with something most people can relate to: different types of documents. You can create a generic Document class, and then a series of subclasses: Letter, Memo, SummaryReport, DetailedReport, Thesis, Resume, Timesheet, LetterOfComplaint, whatever.

In my case, I made the code handle a lot of formatting tricks, and produce output in a variety of formats.

Whatever you choose, I think the key is to make it something you might actually want to use. That's the only way you'll keep using it in the long run.

buckaduck

In reply to Re: Beginner's Object Orientation Exercises? by buckaduck
in thread Beginner's Object Orientation Exercises? by munchie

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


No such thing as a small change
	PerlMonks