Maybe it might help for everyone to take a step back. Everything in this thread, so far, are partial overly-detailed answers to a bigger question. A question I haven't seen being asked (though admittedly I may have missed it). ** What is our goal of Perl tutorials? ** The answer to this determines everything else. My opinion, for what it's worth, is... A tutorial should make the newcomer fall in love with Perl, and want to use it more. It should dangle a carrot, enticing them into a brisk walk, then throw it in the direction of more substantial references for them to jog toward. A tutorial isn't a marathon. It's a slow, gentle, and appealing walk. It is OK to leave out details. Of course there's more than one way to do it, but a newcomer doesn't need to see them all on day 1. That's what references, and search.cpan.org are for. If Dave's submission otherwise meets our goal for an OO Perl tutorial, and does so better than blessed hashes can (and I wholeheartedly believe it does)... then who cares about CPAN dependencies? This is a 15 second hurdle for a newcomer reading through a tutorial which pays off tenfold in its elegance, simplicity, appeal, and just plain sexiness. If relying on CPAN is the big reservation here, we need to weigh how much a core-Perl OO tutorial serves our goal vs. how much the CPAN dependency takes away from our goal.Thread Previous | Thread Next