First off, chip++ for that code.

I had always heard that you can't use references as keys, but nobody said you can't use the string that represents the reference as a key. So, for a naive test, i tried this: 

use strict;

my %TEMPS;
my $max = 1_000_000;

Foo->new() for (0..$max - 1);

print "ok\n" if $max == scalar keys %TEMPS;

package Foo;

sub new {
    my $self = {};
    $TEMPS{ $self->{ID} = "$self" } = $self;
    return $self;
}

[download]
My reasoning was that if the number of objects i created equals the number of keys in the hash that contains them, no duplicate id's were used. The result was "ok" ...

jeffa 

L-LL-L--L-LL-L--L-LL-L--
-R--R-RR-R--R-RR-R--R-RR
F--F--F--F--F--F--F--F--
(the triplet paradiddle)

In reply to (jeffa) Re: Using stringified refs for unique IDs? by jeffa
in thread Using stringified refs for unique IDs? by Masem

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.