...a comment as such coming from an Anonymous Monk leaves much ambiguity... are you being sarcastic?

If you could be so bold, state *why*.

Steve

Because you can. It will help you and your code. You get free testing on many platforms and versions of Perl. Everything else is gravy. Will others find the code useful? Hope so. If not, so what? You find it useful and it's good practice and experience to CPAN stuff. Go for it and have fun!

Ok, Mom ;)

To be honest, I expected both a bit of resistance, and some "what you need to do first..." type feedback before I went ahead with it.

Thanks to Mom ( sorry ), the other posters, and to all those who have helped me throughout the years via other mediums.

Prior to publishing my code publicly, I'd like to officially say to all of the authors of books, docs, snips, sites, replies, papers etc that I can't thank you enough for what you've taught me, and it's my own mental issues that caused the code to come out the way it did, not you.

...stevieb, running off to read more about the details of cpan...

-stevieb

...and it expands your horizons and imposes disiplines that you might otherwise miss. All that guff you have read about testing and documentation suddenly becomes relevant.

A plea though: a CPAN module is for life, not just for Christmas. Please only put stuff on CPAN if you intend to maintain it and look after your users. When you place a module on CPAN you take on a responsibility.

Thanks cdarke,

I truly appreciate the feedback. It's going to take me a month to get everything together, de-customize certain aspects and better my documentation.

That in itself will be a learning and betterment experience, so once that is done, I'll have a better idea of where things should go.

Point well taken about the commitment/responsibility angle, and if I do put the code on CPAN, it will be because I'm ready and prepared for such a task.

Cheers,

Steve

CPAN purpose is code sharing, why wait?