>>>>> "Tim" == Tim Bunce <[EMAIL PROTECTED]> writes:
>> Your name space point is a valid one. DBI solves this by tying the hash >> and only allowing new keys to be added if prefixed with 'private_'. Tim> And I'll be tightening up the docs for that to make specific Tim> recomendations for subclasses to use 'private_<classname>_*'. The problem with encouraging subclassing by documenting it is that you are forever locked in to using a hashref, and thus cannot switch to an arrayref in the future should you decided to do that for space or speed. If people want per-DBI-handle data, why not provide the data via $dbh->private instead, which returns a hashref unique to the handle? Then I can stash stuff there, including behavior using coderefs, without interfering with the type or operation of $dbh->OtherMethods ? -- Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095 <[EMAIL PROTECTED]> <URL:http://www.stonehenge.com/merlyn/> Perl/Unix/security consulting, Technical writing, Comedy, etc. etc. See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
