Re: New module; Exec-RSE?
I' ve actually submitted under the name 'Getopt::Plus' now. Will the next release be called 'Getopt::Plus::Plus' ? :) -J
Re: New module; Exec-RSE?
Sorry about the empty message. What about Getopt::Easy or Getopt::Simple? -J -- On Mon, 2 Dec 2002, Martyn J. Pearce wrote: On Sat, Nov 30, 2002 at 04:22:11PM +1100, Ken Williams wrote: I suggest something like GetOpt::Unified or GetOpt::Common or something. But don't take a really good namespace unless you plan on maintaining it. ;-) Fair point :-) I warm to Getopt::StdResource, and Getopt::Plus. Any votes out there? Mx.
Re: New module; Exec-RSE?
On Sat, Nov 30, 2002 at 04:22:11PM +1100, Ken Williams wrote: I suggest something like GetOpt::Unified or GetOpt::Common or something. But don't take a really good namespace unless you plan on maintaining it. ;-) Fair point :-) I warm to Getopt::StdResource, and Getopt::Plus. Any votes out there? Mx.
RE: New module; Exec-RSE?
On Wed, 27 Nov 2002, Hugh S. Myers wrote: Clever of you to miss the point entirely. That being to put it in the GetOpt namespace---the rest is up to the author... Clever of you to miss that I did get your point entirely. :) I agreed with you which is why I made my example in the GetOpt space. I read an article recently talking about not using strange acronyms in module names and that's why I commented. I responded to your e-mail since I was trying to build on what you had correctly pointed out! Sorry for not making that clearer. RSE just makes me think of some strange IBM acronym. VERA gives us Removable Storage Elements and Research and Systems Engineering as previous uses for RSE. Who could guess the difference between GetOpt::RSE and GetOpt::JCL? -- /chris Programming is a Dark Art, and it will always be. The programmer is fighting against the two most destructive forces in the universe: entropy and human stupidity. They're not things you can always overcome with a methodology or on a schedule. -Damian Conway, Perl God
New module; Exec-RSE?
Dear module authors, I hgave a new module to upload, but am more than a little unsire about the appropriate name. The module is a set of Resources for Standard Executables. It's a bit like GetOptions on steroids; indeed, it is a large user of Getopt::Long, Pod::Usage, and Log::Info. It provides a way for executables to quickly and easily set up option handling, with a number of standard options, which also provide self-documentation (e.g., --help, --man options), and options for controlling the output (via Log::Info). The Getopt::Long is configured, and the calling sequence for arguments is controlled in one place. In this way, all executables using this module perform in a standard way, documentation (e.g. for options) is kept in one place (I was frustated duplicating it), description for general option-handling semantics is kept in one place, etc. This module is not mere theory; it has been used extensively successfully at my place of work for some time now. So, as a starting strawman, I propose Exec::, since it is for executables, RSE, as in Resources for Standard Executables. Hence, Exec-RSE. Does anybody have a better suggestion? Mx.
