...when it gets reimplemented as a value stored in a database somewhere, or stored remotely, such that you access it via SOAP or HTTP or carrier pigeon...or as a value in a hash or array somewhere. But you don't have a need to know...
A procedural interface, whether a get and set pair, or a polymorphic accesser/mutator, provides a way to obtain and change the value while keeping your actions decoupled from the specific storage mechanism.
In reply to Re^6: regex transforms of object attributes
by herveus
in thread regex transforms of object attributes
by Tuppence
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |