Hi,
What about DB_File::Clean instead? Either you have a function to which you
can give diffrent types of cleaning operations or you may have multiple
modules to do the different operations. As an example (certainly incorrect
as I don't have the slightess clue of what you can clean in a DB file), you
could have DB_File::Clean::HashKeys, DB_File::Clean::HashData,
DB_File::Clean::Something.
You could also have this type of interface if you wish to:
use DB_File::Clean ;
DB_Clean( $handle to db, qw(DB_File::Clean::Hash Data
DB_File::Clean::Something)) ;
or
DB_Clean( $handle to db, qw( HashData Something)) ;
and your module would automaticaly load the special cleaning modules passed
as parameters. This is what I do in one of my modules.
# loads Data-TreeDumper-Renderer-DHTML automatically.
DumpTree($tree, 'Tree', RENDERER = 'DHTML');
Cheers, Nadim.
Luis Tello [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
Hello,
My name is Luis. I have been using a
module called DB_File::Lock for the past year on a
project. I was asked by my employeer to develop a way
to remove data not associated with a hash in a dbm
file. The objective was to streamline a dbm file
because using the remove function only removes the
hash and not the data associated to the hash.
I was successful in creating the module and now I
want to prepare it for distribution. Under the advice
of the PAUSE page, I am asking for your perspective on
a namespace. I was think DB_File::GarbageRemoval or
DBM::GarbageRemoval. What do you think?
thanks,
Luis
__
Do you Yahoo!?
Yahoo! Mail is new and improved - Check it out!
http://promotions.yahoo.com/new_mail
