On Tue, 2004-01-20 at 01:55, khemir nadim wrote:
> I don't understand what the autoloading mechanism has to do with
> inheritance! (Something for me to learn I guess)
I think its that as soon as you have AUTOLOAD defined, you can't
inherit past that point, at least by the ISA mechanism: the AUTOL
On Tue, 2004-01-20 at 06:23, Fergal Daly wrote:
> Not that this would ever be agreed upon, the old way is ingrained. Modules
> will continue to do for example
>
> PREREQ_PM => { Parse::RecDescent => 1.80 }
>
> then fall over because 1.90 satisfies this requirement but is not actually
> compatible
On Tue, 2004-01-20 at 07:41, A. Pagaltzis wrote:
>
> I was unclear. What I am talking about is that there is no
> provision to have Foo::Bar 0.11, Foo::Bar 0.42 and Foo::Bar 1.23
> all available in the same installation of Perl. There are some
> modules like only.pm that impose their own conventio
In consideration of what Fergal said, should every public method or function in
a module be individually versioned? So, when I do
use Text::Balanced qw(extract_multiple extract_codeblock), 1.95;
this could (under new semantics) assert only that those two functions have the
same interface and
If you could tell us more about the functionality of the module, that would
help us comeup with more useful feedback.
From: "Ruslan U. Zakirov" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: [Class::MultiList] Need feedback for first distribution
Date: Mon, 19 Jan 2004 21:09:07 +0300
On Tue, Jan 20, 2004 at 10:26:30AM -0500, Mark Stosberg wrote:
> On Tue, Jan 20, 2004 at 12:23:09PM +, Fergal Daly wrote:
> >
> > Not that this would ever be agreed upon, the old way is ingrained. Modules
> > will continue to do for example
> >
> > PREREQ_PM => { Parse::RecDescent => 1.80 }
>
On Tue, Jan 20, 2004 at 12:23:09PM +, Fergal Daly wrote:
>
> Not that this would ever be agreed upon, the old way is ingrained. Modules
> will continue to do for example
>
> PREREQ_PM => { Parse::RecDescent => 1.80 }
>
> then fall over because 1.90 satisfies this requirement but is not actual
* Fergal Daly <[EMAIL PROTECTED]> [2004-01-20 14:34]:
> On Tue, Jan 20, 2004 at 12:17:51PM +0100, A. Pagaltzis wrote:
> > Perl does not provide for keeping around same-named modules
> > that differ in some other way.
>
> That's not true. There are many modules where for example
> version 1.xx has
On Tue, Jan 20, 2004 at 12:17:51PM +0100, A. Pagaltzis wrote:
> Perl does not provide for keeping around same-named modules that
> differ in some other way.
That's not true. There are many modules where for example version 1.xx has
one interface and 2.xx has a different interface and then 2.xx whe
* Martyn J. Pearce <[EMAIL PROTECTED]> [2004-01-20 12:02]:
> Version numbering works great for linear systems, which
> generally occur only with single authorship. If you do your
> own version of Term::ProgressBar, and call it 3.00, and someone
> else does too, they will probably call it... 3.00.
On Mon, 19 Jan 2004 11:03:05 -0600 (CST), Chris Josephes wrote:
> On Mon, 19 Jan 2004, Mark Stosberg wrote:
> > And what happens when module author gets married and get a new
> > hyphenated last name?
>
> How often do CPAN ids really change? I doubt that an extablished author
> would extend his
* Chris Josephes <[EMAIL PROTECTED]> [2004-01-20 12:02]:
> In most cases, you'll only refer to the full name of the module
> once.
Then why would it even matter that much?
> The idea of organizing namespaces is to resolve the issues CPAN
> maintainers have had with naming conflicts, or namespace
Hi Ruslan
> My ideas:
> 1) May be it's better to prefix with _ all funcs which have AUTOLOAD
> magic? There is many such methods in module so it's hard to inherit this
> object.
Thats just one idea, where are the others? I agree with David, It's
difficult to give any opinion if we don't have acce
On Mon, 19 Jan 2004, Daniel Staal wrote:
> Basically, adding the author's name into the name of the module just
> trades an illusion of a 'clean' TLD for my headspace. I would rather
> have a messy TLD: there are tools that can help me search and sort
> that. Perl is *supposed* to help me clean
Mark Stosberg wrote:
I tend to look for new modules by keyword search anyway.
I've been wanting to do something for the CPAN system. I often find the
"SEE ALSO" section of modules to be incomplete. I was hoping that it
would be possible to make RELATED MODULES a basic part of the webpage
th
On Mon, Jan 19, 2004 at 11:05:31AM -0600, Chris Josephes wrote:
> Version numbering is an authorship issue. If I took over module Widget
> from author XYZ, I'd probably use higher version numbers than author X
> used to signify a newer release. To be sure, I'd also include POD
> documentation ide
On Mon, Jan 19, 2004 at 11:03:05AM -0600, Chris Josephes wrote:
> Why would that be? I mean, the odds are if you're dealing with a non-core
> Perl module, you're going to need to know the name if you want to download
> it in the first place. If you use a module long enough, you'll get used
> to h
17 matches
Mail list logo
