Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • The first thing you need to do is work out your goals, then put together a simple prototype.

    Don't waste your time trying to get it exactly right first time, you'll always miss something, and have to refactor and change later anyway.

    Once you have your prototype and your goals you can start work on your documentation, from this you can trivially get your tests, which define your api, which defines how it will work from the outside which will make it clear how it should be structured inside.

    Then you just keep on working on the documentation, tests, etc and it will be pretty clear how it should work and how to structure it.

    There are some very useful tools to help with this - Class::Accessor, Class::DBI, Class::Attribute, etc.

    Its probably worth looking around for some object oriented design books and spending some time learning how to design classes and relationships properly or at least in a structured way the same as you normalise your database - you do normalise your databases don't you?

    --

    @JAPH = qw(Hacker Perl Another Just);
    print reverse @JAPH;