On Tue, 14 Mar 2006 16:52:18 +0100, David Landgren <[EMAIL PROTECTED]> wrote:
> Hey! It's been over two months since we last had one of these suggestions! > > I did battle with a module that shall remain nameless the other day. I > had a difficult time figuring out how to use it. In times like these, I > like being about to go to the build directory and p(aw|ore) through the > eg/ directory and take a script and bend it into a suitable shape. or /examples or /scripts Depending on the type of module, some can supply you with complete working scripts (Tk, Spreadsheet::Read, XML::Twig), and some can't (DBI). Tk installs "widget" for you, in wich you can find most of the basic operations, whereas DBI has superb documentation that has examples and example code scattered all through it. So I don't think the mere existance of /eg (and some content) is worth more qualitee. > The package in question didn't have an eg/ directory, so I had to spend > far more time studying the source and running it through the debugger > than I really cared to. > > For instance, I know that when I have something tricky to do with > HTML::Parser, I know there's always going to be something close to what > I need to do in the eg/ directory. I think its a good adjunct to POD, > which tends to be more (or should be) more theoretical. > > /eg scripts are a nice "hands-on" way of finding out how a module works > in real life. > > No distribution should be without one! /me mumbles Acme -- H.Merijn Brand Amsterdam Perl Mongers (http://amsterdam.pm.org/) using & porting perl 5.6.2, 5.8.x, 5.9.x on HP-UX 10.20, 11.00, 11.11, & 11.23, SuSE 10.0, AIX 4.3 & 5.2, and Cygwin. http://qa.perl.org http://mirrors.develooper.com/hpux/ http://www.test-smoke.org http://www.goldmark.org/jeff/stupid-disclaimers/
