Re: Re: Re: Re: Reducing Perl OO boilerplate

[exussum0]

Nononon.. you missed the point. If I have a program that uses class Foo, and in my program somewhere else, i declare sub new, doing new Foo will break. It's not "why is the constructor called new" but if you do "new Foo" and new() exists on the same scope of your program. Take this for example:

use Foo;

sub new(*)
{
 die "wuh?";
}

$x = new Foo();

With a package..

package Foo;

sub new
{
   return bless { a => 1 }, shift;
}

sub new2
{
   return bless { a => 1 }, shift;
}
1;

new2 works, new breaks. THAT is my point. Why would anyone do this, I don't know. But people have pointed out that ->new is the better convention.

So before you berate me more on what a constructor is, i suggest you reread my posts. Thank you.