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

use Perl

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.

Without JavaScript enabled, you might want to use the classic discussion system instead. If you login, you can remember this preference.

first make it work (Score:2)

by TeeJay (2309)

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

--

@JAPH = qw(Hacker Perl Another Just);
print reverse @JAPH;
Is OOPerl the issue? (Score:1)

by Lunchy (2672)

I've had issues like this as long as I've been programming (perl for 5 years, c++ for 4ish), and for myself at least, these are design and implementation issues and not really language or OO issues. I'm a slow learner, so things seem to finally be jelling for me. I recently purchased the GoF, (gang of four), book on Design Patterns [barnesandnoble.com], and it answered a lot of questions I've had for years about certain code design aspects, especially relating to GUI code design, but I think it also applies more generally. N