in reply to Save a statement handle to a file and open it again as a 'cursor' or something.

Incase it's unclear, i'm being helpful and friendly in this post ;)

I think your code is a bit short on documentation, for hwo the methods act, and what they are for.

Also, you may be interested in reading up on Test::More and Test for the writing of some simple tests to show it works.

(1) If you're planning on unleashing it on CPAN, perlnewmod, perlmodstyle, perlmod and perlmodlib quoth freenode's perlbot

Also, your question is quite open ended, what are you looking for feedback on, specifically? the API, the implementation of the fetch method, or just the indenting style you're using?

@_=qw; ask f00li5h to appear and remain for a moment of pretend better than a lifetime;;s;;@_[map hex,split'',B204316D8C2A4516DE];;y/05/os/&print;

Updated
  1. In Re^4: Save a statement handle to a file and open it again as a 'cursor' or something., jdporter points out that some of my perldoc:// were cpan:// links. They aren't any more.

Replies are listed 'Best First'.
Re^2: Save a statement handle to a file and open it again as a 'cursor' or something.
by uber_spaced (Novice) on Aug 23, 2007 at 18:48 UTC
    I'll be reading these tonight. It looks like following links:

    http://search.cpan.org/search?mode=module&query=perlmod

    http://search.cpan.org/search?mode=module&query=perlmodlib

    arent functioning as you expected.

        I think the point is that f00li5h accidentally wrote [cpan://perlmod] and [cpan://perlmodlib] rather than [doc://perlmod] and [doc://perlmodlib]. We know he knows how to do it right, as he wrote the first two correctly.

      Should have read the "Node text goes above here" thing. That's why the rant about sanity checks is above my statement. Whoops.