Re^2: Getting rid of "new" (superfluous reference constructor)--

and I'm even optimistic that such could be done for Perl 5. But, for now, a good approach is something like:

use Data::Heap::Whatever 1.1 ( \my $Heap
[download]

That reference constructor there is a nit for me. Why should the user be required to provide it? There is no functional reason that it is needed. The import routine should get an alias to the whatever was passed in so I cant really see a reason for it.

Sorry, but I've encountered this design choice a lot (DBI does it somewhere iirc) and it always kind of irritates me as it seems to me to be so unperlish.

---
$world=~s/war/peace/g

Comment on Re^2: Getting rid of "new" (superfluous reference constructor)-- Download Code

Replies are listed 'Best First'.
Re^3: Getting rid of "new" (superfluous reference constructor)-- by tye (Sage) on Jul 07, 2006 at 15:59 UTC
An alternative: `use Data::Heap::Whatever 1.1 ( Factory => my $Heap, ...` [download] But the passing of a reference has two purposes: It lets us reliably distinguish between an option name and a variable being passed in to receive a factory, thus allowing the more stream-lined usage It makes the fact that $Heap will be modified explicit, serving as a form of documentation I don't have a strong preference (other than wishing use could return a factory), though. - tye	[reply] [d/l]

Replies are listed 'Best First'.

Re^3: Getting rid of "new" (superfluous reference constructor)--
by tye (Sage) on Jul 07, 2006 at 15:59 UTC

An alternative:

use Data::Heap::Whatever 1.1 ( Factory => my $Heap, ...
[download]

But the passing of a reference has two purposes:

It lets us reliably distinguish between an option name and a variable being passed in to receive a factory, thus allowing the more stream-lined usage
It makes the fact that $Heap will be modified explicit, serving as a form of documentation

I don't have a strong preference (other than wishing use could return a factory), though.

- tye

[reply]
[d/l]