As in
a's comment, I also tend to write top down using
wishful
programming. (Where wishful programming is using names
of functions I haven't written yet.) This has the benefit
of not having to think about everything at once, and
if you create stub functions it will actually run and you
can slowly build it up. Ah ha, starting to use some XP
techniques! (Except I learnt to do this before XP was
around...)
When it comes to breaking functions up,
if I have a function which is trying to do several different
things, it is usually time to break it up. Likewise, a
function which is more than a couple of screens long is
about due for a break up. Although the screens one is very
relative... Especially when I'm writing CGI scripts which
are generating forms, they can get rather lengthy.
Over the last couple of weeks I've been writing a interface
for managing Spong -
using Perl OO. In an object, if I realise that I need to
use
some code again (for example: sucking details out of
the database about a host), it get's broken out to a new
function in the object.
So, there's some of my approaches. Of course, if I sat
down and did some decent design before hand I'd only need
to use the first one - wishful programming - as the functions
would already be broken up logically.
Sigh...
Updated: Right, that link to Spong now works as it
should. My bad. (Thanks a for pointing it out!)
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.