I must admit that whenever I've been coaching people on creating new objects, I almost always tell them to declare an object like this:

my $objectBlah = Blah::Object->new();
[download]

I guess my reasoning behind this is that you should always be clear on creating a new instance of an object. I can't think of too many instances where I'd do

my $foo = $bar->new();
[download]

...that just wouldn't, generally, cut the mustard with me -- unless you *really* needed another instance of the same object to do other stuff with. As I write this, I was trying to think of when I've needed to do this exact thing, and I honestly can't think of any instances that I've done that.

However -- that may merely be an indictment of how I like to design my objects and code, generally.....!

Also, I, personally dislike the following syntax:

my $foo = new Bob::Object;
[download]

I can't think of an exact reason -- probably just that I think that perl's syntax is nearly always based around using something like (in the case of reading a constant item that you've set up in your object framework) :-

my $constantStuff = Bob::Constants::CONSTANT_STUFF;
[download]

Adding in something like this:

my $bob = new Bob::Object;
[download]

...just doesn't fit (in my head at least) with the nice perl way of doing things.

I know my reason doesn't make too much sense: I just like a bit of consistency........!

PS I'm actually really enjoying this conversation about something as simple as the best new() function to use. It reminds me of why I love perl so much.......!