----- Forwarded message from Tom Christiansen <[EMAIL PROTECTED]> -----
To: Jarkko Hietaniemi <[EMAIL PROTECTED]>
cc: [EMAIL PROTECTED], Peter Prymmer <[EMAIL PROTECTED]>
Subject: Re: perldoc for you?
In-Reply-To: Message from Jarkko Hietaniemi <[EMAIL PROTECTED]>
of "Fri, 08 Sep 2000 18:48:38 CDT." <[EMAIL PROTECTED]>
Date: Fri, 08 Sep 2000 18:06:02 -0600
Message-ID: <22859.968457962@chthon>
From: Tom Christiansen <[EMAIL PROTECTED]>
>> > It was the perl module stuff. I can't for the *life* of me get
>> > an answer about what to do about this from the namespace czars.
>I'll run the issue by other czars.
The issues are several.
What is the namespace to use for pod related utilities and
libraries? Should it be something like Pod::Tools::podgrep?
Or Pod::Utils::podpath? Or something else, like Tools::Pod
or PodTools? How many should be merged into one, allowing
imports like Pod::Tools qw/podpath/? This is not very
extensible though.
What is the namespace to use for Perl-Module-related utilities
and libraries? Should it be something like PM::Tools::pmeth,
PM::Tools::pmpath, etc?
What about the Perl Power Tools stuff, that is, the standard
Unix tools replacements? PPT::tcgrep is weird, because what's
"PPT"? And if it's replacing grep, oughtn't we call it grep?
No, can't do that -- can't import a grep function. Should it
be PPT->main("tcgrep") or something? I'm not sure that helps.
Note that this is the i/f for simu-exec'ing, not the same as a
per-line in-out filter equiv.
Does or should the fact that these all files are a superpositioning
of a Perl module *and* its documentation *and* an executable
standalone Perl program have any effect on the decisions about
the previous three questions?
--tom
----- End forwarded message -----
--
$jhi++; # http://www.iki.fi/jhi/
# There is this special biologist word we use for 'stable'.
# It is 'dead'. -- Jack Cohen
