In Thoughts on script portability I touched upon some of the reasons why you might "re-invent the wheel." Sometimes all you have are sticks and stones and you have to be inventive.

I can think of another reason you might want to re-invent the wheel. If you have a crusty professor like I am when I am teaching you are darn sure going to end up re-inventing the wheel.

When I was teaching Perl to college students I often would pose a problem to them, for instance (right out of my lesson plan:)

Write a script to parse an input file and create a tree
of HTML elements and their leaf nodes.
[download]

Now if I had to solve that problem in the real world I would be looking to CPAN in the HTML::* space for the right module. But for someone learning Perl it is a good intellectual excercise to have to invent that wheel and program for it.

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

Outside of code tags, you may need to use entities for some characters:

	For:		Use:
	&		&
	<		&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.