|
|
| Think about Loose Coupling | |
| PerlMonks |
Re^2: Is "ref($class) || $class" a bad thing?by hardburn (Abbot) |
| on Jul 12, 2004 at 16:29 UTC ( #373650=note: print w/ replies, xml ) | Need Help?? |
|
Basically, that construct is saying "This method can be called as either a class or instance method". merlyn's writings have been against using this in constructors specifically, not against using it in general methods to allow it to be called against both a class and an object. This is because a chunk of programmers out there expect it to act as a clone, another chunk thinks it should act as a copy, and yet another chunk thinks it should be an error. I go for something like this:
----
In Section
Meditations
|
|
||||||||||||||||||||