|
Posted by matthias.eckardt on September 30, 2004, 3:06 am
Please log in for more thread options
Hi. I'm considering adding a new module to CPAN and want some
feedback.
The goal of the module is to support the small scripts you have to
write
every day. These functionality is available yet:
- GetOpt style command line processing with mandatory check, default
values,
automated usage messages.
- help function with automated POD display
- simple logging
- simple read/write of entire files from/to arrays with error handling
- simple formatter for data in CSV, array or DBI datastructures
- simple signal handling
- IO::File open with error logging
What I need is a name space for this. Today I use EUB. It's a acronym
of the name of my company. I know that's not at all a good idea.
Can anybody help?
Thank's.
Matthias
|
|
Posted by Christian Winter on September 30, 2004, 4:40 pm
Please log in for more thread options
matthias.eckardt@link-up.de wrote:
> Hi. I'm considering adding a new module to CPAN and want some
> feedback.
> The goal of the module is to support the small scripts you have to
> write
> every day. These functionality is available yet:
>
> - GetOpt style command line processing with mandatory check, default
> values,
> automated usage messages.
> - help function with automated POD display
> - simple logging
> - simple read/write of entire files from/to arrays with error handling
> - simple formatter for data in CSV, array or DBI datastructures
> - simple signal handling
> - IO::File open with error logging
>
> What I need is a name space for this. Today I use EUB. It's a acronym
> of the name of my company. I know that's not at all a good idea.
Normally I'm not a friend of new toplevel namespaces, but as
I don't see your module fit into any existing one[1], how about
Script::Toolbox? There is already a Module:: namespace, so this
would in some way counterpart it.
HTH
-Christian
[1] I didn't memorize all of CPAN archive, so don't beat me if
I missed something obvious ;-)
|
|
Posted by matthias.eckardt on October 4, 2004, 6:04 am
Please log in for more thread options > matthias.eckardt@link-up.de wrote:
> > Hi. I'm considering adding a new module to CPAN and want some
> > feedback.
> > The goal of the module is to support the small scripts you have to
> > write
> > every day. These functionality is available yet:
> >
> > - GetOpt style command line processing with mandatory check, default
> > values,
> > automated usage messages.
> > - help function with automated POD display
> > - simple logging
> > - simple read/write of entire files from/to arrays with error handling
> > - simple formatter for data in CSV, array or DBI datastructures
> > - simple signal handling
> > - IO::File open with error logging
> >
> > What I need is a name space for this. Today I use EUB. It's a acronym
> > of the name of my company. I know that's not at all a good idea.
>
> Normally I'm not a friend of new toplevel namespaces, but as
> I don't see your module fit into any existing one[1], how about
> Script::Toolbox? There is already a Module:: namespace, so this
> would in some way counterpart it.
>
> HTH
> -Christian
>
> [1] I didn't memorize all of CPAN archive, so don't beat me if
> I missed something obvious ;-)
Script::Toolbox sounds good. I think my module would not fit in the
Module:: namespace. It does not support the handling of modules.
|
|
Posted by brian d foy on October 4, 2004, 3:50 pm
Please log in for more thread options [[ This message was both posted and mailed: see
the "To," "Cc," and "Newsgroups" headers for details. ]]
> Script::Toolbox sounds good. I think my module would not fit in the
> Module:: namespace. It does not support the handling of modules.
I like it. Request the namespace through PAUSE and I will approve
it.
--
brian d foy, comdog@panix.com
|
|
Posted by Jim Keenan on October 2, 2004, 11:50 pm
Please log in for more thread options matthias.eckardt@link-up.de wrote:
> Hi. I'm considering adding a new module to CPAN and want some
> feedback.
> The goal of the module is to support the small scripts you have to
> write
> every day. These functionality is available yet:
>
> - GetOpt style command line processing with mandatory check, default
> values,
> automated usage messages.
> - help function with automated POD display
> - simple logging
> - simple read/write of entire files from/to arrays with error handling
> - simple formatter for data in CSV, array or DBI datastructures
> - simple signal handling
> - IO::File open with error logging
Are you sure you want all this different functionality in one module?
>
> What I need is a name space for this. Today I use EUB. It's a acronym
> of the name of my company. I know that's not at all a good idea.
>
> Can anybody help?
Procedural suggestion: Post this query on the module-authors@perl.org
mailing list. You'll get plenty of feedback.
jimk
|
| Similar Threads | Posted | | Adding installable script to a perl module distro? | August 30, 2005, 7:24 pm |
| Adding a .pl to @INC | July 5, 2006, 3:57 am |
| Adding XSLT information to XML generated by DBIx::XML_RDB | July 20, 2008, 10:00 am |
| After adding some Perl modules in my SuSE 8.2 installation Amavis does not function anymore. | December 12, 2004, 2:04 pm |
| Getting a module on CPAN | June 7, 2007, 4:28 pm |
| how do I package a CPAN module? | October 23, 2004, 1:13 pm |
| It's not PHP, is it? (potential new CPAN module) | July 21, 2007, 3:16 am |
| Problem gettting module from CPAN | September 19, 2004, 9:56 pm |
| CPAN Errors Installing Tk Module | November 26, 2004, 9:56 pm |
| Installing a CPAN Module online | June 26, 2005, 8:45 pm |
|
XML Sitemap