Re: Namespace suggestions for new module submission
On Thu, Jan 01, 2004 at 06:15:49PM -0900, Arthur Corliss wrote: Greetings: In the near future I'd like to submit a module for inclusion on CPAN. I need some advice on the appropriate namespace, however, since I don't want to pollute top-level namespace. Unofficial module name (as it's being developed): PerlDBM Synopsis: Pure-perl implementation of a dbm engine. Supported only on platforms with 64-bit filesystems. Database files are portable (all data is stored in network-byte order), with record-level locking and transactions. Has it's own API for low-level control, but also will support tied hashes. I did notice that most of the XS wrappers for C-based implementations were all in top-level namespace, though. Any suggestions/preferences? Will this be implemented with the DBI interface? Then DBD::YourProject seems appropriate. DBD::SQLite seems to be a related case, although it's not Pure Perl, it just allows you install it as a standard DBI driver. Mark
Re: Namespace suggestions for new module submission
On Fri, 2 Jan 2004, Mark Stosberg wrote: Will this be implemented with the DBI interface? Then DBD::YourProject seems appropriate. DBD::SQLite seems to be a related case, although it's not Pure Perl, it just allows you install it as a standard DBI driver. I don't think it does enough to warrant inclusion in DBD::*, nor have I planned to make it accessible via DBI. It's just another method for disk-based stateful hashes, like all the *DBM_File modules. Modules like AnyDBM_File and DB_File are causing some unpredictable results in some of my code, depending on the version and implementation of the dbm libs they're linked against. This is just my way of getting predictable results without requiring admins to upgrade or install new system libs, along with the requisite Perl modules. --Arthur Corliss Bolverk's Lair -- http://arthur.corlissfamily.org/ Digital Mages -- http://www.digitalmages.com/ Live Free or Die, the Only Way to Live -- NH State Motto
