Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

barbie (2653)

barbie
  reversethis-{ku. ... m} {ta} {eibrab}
http://barbie.missbarbell.co.uk/

Leader of Birmingham.pm [pm.org] and a CPAN author [cpan.org]. Co-organised YAPC::Europe in 2006 and the 2009 QA Hackathon, responsible for the YAPC Conference Surveys [yapc-surveys.org] and the QA Hackathon [qa-hackathon.org] websites. Also the current caretaker for the CPAN Testers websites and data stores.

If you really want to find out more, buy me a Guinness ;)

Links:
Memoirs of a Roadie [missbarbell.co.uk]
[pm.org]
CPAN Testers Reports [cpantesters.org]
YAPC Conference Surveys [yapc-surveys.org]
QA Hackathon [qa-hackathon.org]

Journal of barbie (2653)

Tuesday July 16, 2002
07:51 AM

Devel::DebugPrint

[ #6387 ]
So I'm finally getting closer to finishing my little module for managing debug output files. A nice little noddy module that I have been using in various forms since 1985 when I started writing C libraries.

Originally it was to be Devel::Debug, but after an email from another author, I discovered that perhaps that wasn't really a good name. Not sure if DebugPrint.pm is the right name, but it does better describe what it does.

I have another module on the horizon, but I'm not sure if it's that useful to anyone else. Then again it would be nice to see something like it on CPAN.

Anyway, I'm now reading up on the best way to make sure I'm not stepping on any toes etc. The nice thing about CPAN is that it's a huge resource, but when newbie authors, like me, coming along it can be quite daunting to get it right.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.