in reply to Reasons for looking at your favourite module's source
Step-by-step: Preparing the ground
Before we even start scraping out the code,
there are a few things
we'll want to do in advance.
Dig into a bunch of modules to see how they're written. I'd suggest
starting with Text::Tabs, since it's in the standard library and is
nice and simple, and then looking at something like Time::Zone,
File::Copy and then some of the "Mail::*" modules if you're planning
on writing object oriented code.
These should give you an overall feel for how modules are laid out
My personal recommandations would be Template::Toolkit
and CGI::Kwiki. Two architectures that have impressed