Re: Time to Document Callbacks

On Fri, 30 Oct 2009 12:31:03 +0000, Tim Bunce <[email protected]>
wrote:

> On Thu, Oct 29, 2009 at 05:10:07PM -0700, David E. Wheeler wrote:
> > On Oct 29, 2009, at 4:24 PM, Tim Bunce wrote:
> >
> >> I could arrange for Callbacks to only apply to methods called by the
> >> applicationi, and not to 'nested calls'. That's a fairly major change
> >> after this length of time but given the limited use Callbacks have had,
> >> and the lack of documentation, it's not out of the question.
> >>
> >> The downside is that to intercept all fetched rows in a general way
> >> (like some kind of plugin utility module might want to do) you now have
> >> to add callbacks for 7 $sth fetch* methods and 6 $dbh select* methods.
> >>
> >> Is that really preferable?
> >
> > Well, yes.
> 
> Okay. Anyone else care to express an opinion?

So far I didn't really follow. I just assumed that all would go well.
Will any of this influence DBD authors to have to change/add/update
their modules?

> > But if there were 'fetch*' and 'select*' keys that could go to 
> > all of them at once, that would be cool, too.
> 
> Let's revisit that topic when/if post-call callbacks get supported.

-- 
H.Merijn Brand  http://tux.nl      Perl Monger  http://amsterdam.pm.org/
using & porting perl 5.6.2, 5.8.x, 5.10.x, 5.11.x on HP-UX 10.20, 11.00,
11.11, 11.23, and 11.31, OpenSuSE 10.3, 11.0, and 11.1, AIX 5.2 and 5.3.
http://mirrors.develooper.com/hpux/           http://www.test-smoke.org/
http://qa.perl.org      http://www.goldmark.org/jeff/stupid-disclaimers/