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
an endless discussion thread about what features to include.
-- Jarkko Hietaniemi
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
first make it work (Score:2)
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;
Reply to This