I'll just reply to the question in the title. A hash is preferred because it provides a data structure with named access. A subclass, if you can tolerate the knowledge of the superclass's implementation, can easily add hash elements to the progenitor.
That is impure, as OO goes, but it works awfully well.
After Compline,
Zaxo
In reply to Re: Why is a hash the default "object" in oo perl?
by Zaxo
in thread Why is a hash the default "object" in oo perl?
by theAcolyte
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |