[EMAIL PROTECTED] (Damian Conway) writes:
> Larry has previously mentioned the prospect of Perl 6 module names
> being extended to include version number and author.
Yes, we even talked about it extensively at the "CPAN meeting" in
Monterey 2 years ago. =)
--
ask bjoern hansen, http://askbjoer
On Tue, Jun 18, 2002 at 05:32:40PM -0700, Larry Wall wrote:
>
> I expect to end up with a multi-level system, where you can use anything from
> a DNS name (guaranteed to contain dots) through author IDs (no dots) to
> blessed top-level names for universally acclaimed modules, for some definition
On 6/18/02 8:32 PM, Larry Wall wrote:
> I expect to end up with a multi-level system, where you can use anything from
> a DNS name (guaranteed to contain dots) through author IDs (no dots) to
> blessed top-level names for universally acclaimed modules, for some definition
> of universal.
I'm not
On Tue, 18 Jun 2002, John Siracusa wrote:
: On 6/18/02 6:10 PM, Damian Conway wrote:
: > Larry has previously mentioned the prospect of Perl 6 module names being
: > extended to include version number and author.
: >
: > If this were to be done, would seem reasonable for the "author" component to
On 6/18/02 6:10 PM, Damian Conway wrote:
> Larry has previously mentioned the prospect of Perl 6 module names being
> extended to include version number and author.
>
> If this were to be done, would seem reasonable for the "author" component to
> simply be the author's CPAN username. These are g
Larry has previously mentioned the prospect of Perl 6 module names being extended to
include version number and author.
If this were to be done, would seem reasonable for the "author" component to simply be
the author's CPAN username. These are guaranteed unique, are frequently mnemonic, are
n
Larry has previously mentioned the prospect of Perl 6 module names being extended to
include version number and author.
If this were to be done, would seem reasonable for the "author" component to simply be
the author's CPAN username. These are guaranteed unique, are frequently mnemonic, are
n
At 02:10 PM 6/17/2002 -0600, Luke Palmer wrote:
>Java's hell if you know Perl. You're used to doing things in 200
>keystrokes, and suddenly it takes you 5000. "The easy things should be
>long, and the hard things should be longer... and slower." (i.e. I don't
>like Java)
If you don't have the b
On Mon, 2002-06-17 at 16:10, Luke Palmer wrote:
> > So, in order for me to avoid learning Java, I propose
> > that a CPAN "Curation Project", or an Extended
> > Standard Perl Library", be formed.
>
> Or, Standard Extended Library of Perl. SELP is more pronouncable than
> ESPL. SELF is bette
On 6/16/02 1:50 AM, Luke Palmer wrote:
> On Sun, 16 Jun 2002, Michael G Schwern wrote:
>> Let's dump out the sack of namespace partitioning problems:
>>
>> What if Acme decides it wants to release part of it's code as Open Source?
>> (Happens a lot). Does it release it as Com::Acme::Text::Thing
On Sun, 16 Jun 2002, Michael G Schwern wrote:
> On Sat, Jun 15, 2002 at 10:35:48PM -0400, John Siracusa wrote:
> > Once nice thing about Java is the class naming convention that lets
> > individual companies (or even individuals, I guess) do custom development
> > that they can safely integrate w
On Sat, Jun 15, 2002 at 10:35:48PM -0400, John Siracusa wrote:
> Once nice thing about Java is the class naming convention that lets
> individual companies (or even individuals, I guess) do custom development
> that they can safely integrate with the "standard" Java classes and the work
> of other
Once nice thing about Java is the class naming convention that lets
individual companies (or even individuals, I guess) do custom development
that they can safely integrate with the "standard" Java classes and the work
of other companies/individuals without fear of namespace clashes. For
example,
13 matches
Mail list logo
