in reply to Why is a hash the default "object" in oo perl?
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
|
---|
Replies are listed 'Best First'. | |
---|---|
Re^2: Why is a hash the default "object" in oo perl?
by toma (Vicar) on Jul 18, 2004 at 07:35 UTC | |
by BUU (Prior) on Jul 18, 2004 at 09:26 UTC | |
by toma (Vicar) on Jul 19, 2004 at 02:47 UTC | |
by crabbdean (Pilgrim) on Jul 19, 2004 at 23:38 UTC | |
by diotalevi (Canon) on Jul 19, 2004 at 23:47 UTC | |
by diotalevi (Canon) on Jul 19, 2004 at 17:01 UTC |
In Section
Meditations