An extremely good link indeed!

Actually the code examples given there support (IMHO) what I wrote in Re^2: Doubt about fly-weight objects., i.e. that the aspect that is mostly stressed is that of caching. But then again, it wasn't much touched upon in all of the previous examples of flyweight objects I had seen.

This actually raises in me a related question: if it's only for caching, can't one still obtain it with a lexical hash with "standard" objects? I mean, something a' la:

{
    my %seen;

    sub new {
        my $class = shift;
        my ($this, $value)=@_;
        my $id = unique_id $this, $value;
        $seen{$id} ||= bless { THIS => $this,
                               VALUE => $value }, $class;
    }

    # Suitable DERSTROY here...
}
[download]

In other words, the two concepts, i.e. that of caching and that of storing the actual object's data in package lexical "outside" of the object itself are mostly orthogonal. Aren't they?

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.