Well, if you can't see the small parts, work from top down first. I've often coded things as:
my $data = get_data();
process_data($data);
print_result();
literally, as if it were pseudo code. Then I write stub routines, like:
sub get_data {
# returns scalar data pointer to my structure
my $return_value;
my $db = open_database($credentials); # must declare this above
my $data = query_db($db, "select * from bar");
$return_value = massage_data($data);
return $return_value;
}
sub open_database {
my $cred = shift;
warn "open_database doing nothing";
return undef;
}
...
and so on... Then at any time, I can "run" what I've got. And stay focussed on
each area of development. If I need a class, I'll develop a generic class that I can plug in.
Again, the goal is to type a dozen-ish lines of code, then invoke it. That's nearly always been possible.
-- Randal L. Schwartz, Perl hacker
-
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.
|