David Landgren [EMAIL PROTECTED] writes:
Steve Peters wrote:
On Tue, Mar 14, 2006 at 04:52:18PM +0100, David Landgren wrote:
[...]
/eg scripts are a nice hands-on way of finding out how a module works
in real life.
No distribution should be without one!
Unless, of course, it has an
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/
On Tue, Mar 14, 2006 at 04:52:18PM +0100, 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
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
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
Adam Kennedy wrote:
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.
Maybe there should be a Kwalitee metric for the length of the synopsis?
:-)
Regards,
David Golden
Steve Peters wrote:
On Tue, Mar 14, 2006 at 04:52:18PM +0100, David Landgren wrote:
[...]
/eg scripts are a nice hands-on way of finding out how a module works
in real life.
No distribution should be without one!
Unless, of course, it has an examples/ directory, which would cause the
On Tue, Mar 14, 2006 at 12:48:52PM -0500, David Golden wrote:
Adam Kennedy wrote:
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.
Maybe there should be a Kwalitee metric for the
Tels wrote:
Moin,
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.
Plus, the code cut and pasted from Synopses winds up with 8 space
leading
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,
* David Landgren [EMAIL PROTECTED] [2006-03-14 19:05]:
Plus, the code cut and pasted from Synopses winds up with 8
space leading indents or whatever, that you have to strip out
and/or you forget to turn off vi's auto indenting so you have
this massive staircase effect and the last line starts at
* David Landgren [EMAIL PROTECTED] [2006-03-14 16:55]:
No distribution should be without one!
Proc::Fork would definitely not benefit from an eg/ directory.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
Steve Peters [EMAIL PROTECTED] wrote:
/eg scripts are a nice hands-on way of finding out how a module works
in real life.
No distribution should be without one!
Unless, of course, it has an examples/ directory, which would cause the
kwalitee test to fail. ;) I do think its a good
--- Tyler MacDonald wrote:
Well so far the only ones I've seen are eg, examples, and from that
renegade GD::Graph, samples.
And from that eccentric Acme::Bleach, demo.
/-\
On yahoo!7
Avatars: Dress up like your
14 matches
Mail list logo
