The best approach depends on your problem. But for many problems a very good approach is to start with a running program that does nothing like what you need and then through many iterations make it into the program you want. And when I say a running program, there are occasions when I've started with:
#! /usr/bin/perl -w
use strict;
print "Hello, world\n";
and then evolved it into an entirely unrelated program. (I usually start with a slightly more complex standard template that does things like find the right library path, processes command-line arguments, and has POD stubs.)
This approach may seem weird but it can work quite well. Particularly if you mix it with test driven development.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.