BTRIEVE-SAVE

 view release on metacpan or  search on metacpan

SAVE.pm  view on Meta::CPAN

    $save_btr->{'opt'}{'increment'} = -1;

    my $file = $save_btr->{'opt'}{'file'};
    if (not(-e $file)) {carp "File \"$file\" doesn't exist"; return} 
    open (*file, $file);
    binmode *file;
    $save_btr->{'opt'}{'handle'}=\*file; #store filehandle in object
}

###################################################################
# config() looks for a config file which tells us where the
# offsets are in the fixed part of the record, their types and
# what to call them locally.
###################################################################

sub config {
    my $save_btr = shift;
    my $proto_rec = BTRIEVE::SAVE::REC->newconfig($save_btr->{'opt'}{'config'});
    $save_btr->{'opt'}{'proto_rec'} = $proto_rec;
} 

SAVE.pm  view on Meta::CPAN


Please let us know if you run into any difficulties using
BTRIEVE::SAVE--we'd be happy to try to help. Also, please contact us
if you notice any bugs, or if you would like to suggest an
improvement/enhancement. Email addresses are listed at the bottom of
this page. Lane is probably the most interested in making this work, so 
may be your best initial bet.

=head2 BTRIEVE::SAVE::REC structure.

A save file record on disk looks like:

          __________________________________________
          |   Fixed,          | Fixed,   |           |
Count[, ] |   indexed.        | left-over|  Variable |\r\n
          |___________________|__________|___________|

The Count is the number of "boxed bytes" (excluding the count itself, the
following comma or space, and the final two bytes at the end). Count is 
an unpadded ascii integer, like "524".



( run in 0.359 second using v1.01-cache-2.11-cpan-64827b87656 )