What would be the alternative? One program-wide generic object?
sub id { Scalar::Util::refaddr( shift) || 'the_one_generic_object' }
would do that. So would the standard id() function (ignoring possible "uninitialized" warnings) with an empty string instead of 'the_one_generic_object".
I wouldn't put it in terms of "right" and "wrong", but obviously I expect the behavior that has one generic object per class to be more useful. I'd have to build, or at least sketch, some example applications that involve subclassing to see which behavior wins out in practice. At this point it's just my intuition,
but I'm not alone in that.
In his perltooc, Tom Christansen discusses a similar concept for the standard hash-based type of class. The functional equivalent of the generic object is what he calls the eponymous hash. That implementation also provides one such hash per class.
Anno
-
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.
|