Moin, David Landgren 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
Whats the /eg directory you speak of? :D On Tuesday 14 March 2006 18:13, Adam Kennedy wrote: [snip] > I have a shitload of distributions, mostly small components. > > For all those component distributions I consider it a failure if it is > so complex that you need something more than just three or four lines > from the SYNOPSIS. > How about we penalise anything with a eg/example directory, for not > having clear enough documentation, or a clean enough design/API. :) > There's a lot of reasons for not having an eg/ directory, unless your > distribution is huge and complicated, like say bioperl. You are contradicting yourself :) My modules are usually so feature crammed that they need a few examples for showing what you can all do with it or to enable the user oto use the modul without having to write/use perl code first. Best wishes, Tels -- Signed on Tue Mar 14 18:40:44 2006 with key 0x93B84C15. Visit my photo gallery at http://bloodgate.com/photos/ PGP key on http://bloodgate.com/tels.asc or per email. Ich bin mit der Gesamtsituation unzufrieden!
pgpaN87I3Gp1Q.pgp
Description: PGP signature
