PNG  IHDR* pHYs+ IDATx]n#; cdLb Ǚ[at¤_:uP}>!Usă cag޿ ֵNu`ݼTâabO7uL&y^wFٝA"l[|ŲHLN밪4*sG3|Dv}?+y߉{OuOAt4Jj.u]Gz*҉sP'VQKbA1u\`& Af;HWj hsO;ogTu uj7S3/QzUr&wS`M$X_L7r2;aE+ώ%vikDA:dR+%KzƉo>eOth$z%: :{WwaQ:wz%4foɹE[9<]#ERINƻv溂E%P1i01 |Jvҗ&{b?9g=^wζXn/lK::90KwrюO\!ջ3uzuGv^;騢wq<Iatv09:tt~hEG`v;3@MNZD.1]L:{ծI3`L(÷ba")Y.iljCɄae#I"1 `3*Bdz>j<fU40⨬%O$3cGt]j%Fߠ_twJ;ABU8vP3uEԑwQ V:h%))LfraqX-ۿX]v-\9I gl8tzX ]ecm)-cgʒ#Uw=Wlێn(0hPP/ӨtQ“&J35 $=]r1{tLuǮ*i0_;NƝ8;-vݏr8+U-kruȕYr0RnC]*ެ(M:]gE;{]tg(#ZJ9y>utRDRMdr9㪩̞zֹb<ģ&wzJM"iI( .ꮅX)Qw:9,i좜\Ԛi7&N0:asϓc];=ΗOӣ APqz93 y $)A*kVHZwBƺnWNaby>XMN*45~ղM6Nvm;A=jֲ.~1}(9`KJ/V F9[=`~[;sRuk]rєT!)iQO)Y$V ی ۤmzWz5IM Zb )ˆC`6 rRa}qNmUfDsWuˤV{ Pݝ'=Kֳbg,UҘVz2ﴻnjNgBb{? ߮tcsͻQuxVCIY۠:(V뺕 ٥2;t`@Fo{Z9`;]wMzU~%UA蛚dI vGq\r82iu +St`cR.6U/M9IENDB`package SDBM_File; use strict; use warnings; require Tie::Hash; require XSLoader; our @ISA = qw(Tie::Hash); our $VERSION = "1.14"; our @EXPORT_OK = qw(PAGFEXT DIRFEXT PAIRMAX); use Exporter "import"; XSLoader::load(); 1; __END__ =head1 NAME SDBM_File - Tied access to sdbm files =head1 SYNOPSIS use Fcntl; # For O_RDWR, O_CREAT, etc. use SDBM_File; tie(%h, 'SDBM_File', 'filename', O_RDWR|O_CREAT, 0666) or die "Couldn't tie SDBM file 'filename': $!; aborting"; # Now read and change the hash $h{newkey} = newvalue; print $h{oldkey}; ... untie %h; =head1 DESCRIPTION C establishes a connection between a Perl hash variable and a file in SDBM_File format. You can manipulate the data in the file just as if it were in a Perl hash, but when your program exits, the data will remain in the file, to be used the next time your program runs. =head2 Tie Use C with the Perl built-in C function to establish the connection between the variable and the file. tie %hash, 'SDBM_File', $basename, $modeflags, $perms; tie %hash, 'SDBM_File', $dirfile, $modeflags, $perms, $pagfilename; C<$basename> is the base filename for the database. The database is two files with ".dir" and ".pag" extensions appended to C<$basename>, $basename.dir (or .sdbm_dir on VMS, per DIRFEXT constant) $basename.pag The two filenames can also be given separately in full as C<$dirfile> and C<$pagfilename>. This suits for two files without ".dir" and ".pag" extensions, perhaps for example two files from L. C<$modeflags> can be the following constants from the C module (in the style of the L system call), O_RDONLY read-only access O_WRONLY write-only access O_RDWR read and write access If you want to create the file if it does not already exist then bitwise-OR (C<|>) C too. If you omit C and the database does not already exist then the C call will fail. O_CREAT create database if doesn't already exist C<$perms> is the file permissions bits to use if new database files are created. This parameter is mandatory even when not creating a new database. The permissions will be reduced by the user's umask so the usual value here would be 0666, or if some very private data then 0600. (See L.) =head1 EXPORTS SDBM_File optionally exports the following constants: =over =item * C - the extension used for the page file, usually C<.pag>. =item * C - the extension used for the directory file, C<.dir> everywhere but VMS, where it is C<.sdbm_dir>. =item * C - the maximum size of a stored hash entry, including the length of both the key and value. =back These constants can also be used with fully qualified names, eg. C. =head1 DIAGNOSTICS On failure, the C call returns an undefined value and probably sets C<$!> to contain the reason the file could not be tied. =head2 C This warning is emitted when you try to store a key or a value that is too long. It means that the change was not recorded in the database. See BUGS AND WARNINGS below. =head1 BUGS AND WARNINGS There are a number of limits on the size of the data that you can store in the SDBM file. The most important is that the length of a key, plus the length of its associated value, may not exceed 1008 bytes. See L, L, L =cut