Re: BTRIEVE::*

2003-12-18 Thread Tim Bunce
On Thu, Dec 18, 2003 at 03:49:07PM +0100, Steffen Goeldner wrote: I'm still open for namespace suggestions. The following list BTRIEVE::File BTRIEVE::ISAM::File BTRIEVE::ISAMFile BTRIEVE::IsamFile with descending preference comes into my mind. Assuming ISAM is implied

Re: BTRIEVE::*

2003-12-18 Thread Steffen Goeldner
Steffen Goeldner wrote: I understand your objections because each (but the first) retrieval is based on a 'current record' - thus storing that state in a separate iterator object may be a better choice. I rejected that! The documentation says: Btrieve initializes the Position Block when

Re: BTRIEVE::*

2003-12-09 Thread Steffen Goeldner
Whereas the top-level name was fixed to BTRIEVE, I still thought about a convenient second-level name for the pure perl part. Because it provides methods for common Btrieve operations and these are operations on Btrieve files, I'd settle on BTRIEVE::File as module name. A typical usage

Re: BTRIEVE::*

2003-12-09 Thread Steffen Goeldner
Tim Bunce wrote: Close() I can follow, And Open(), I hope ;-) but what are GetEqual and GetNext doing on a 'file' object? These are examples of 'Data Retrieval Operations' (my primary interest!), which return a record from the file. Step*() are physical operations, i.e. StepNext() is

Re: BTRIEVE::*

2003-12-06 Thread Randy W. Sims
:07AM +0100, Steffen Goeldner wrote: Randy W. Sims wrote: Maybe DBMS::BTrieve::??? That looks good! But that's a new namespace. The horse has well and truly bolted on the db module namespace issue. They're all over the place. I think reusing an existing namespace is better than creating yet

Re: BTRIEVE::*

2003-12-05 Thread Steffen Goeldner
Tim Bunce wrote: I don't know (or can't remember) how the BTRIEVE::SAVE module got into the module list, but since it is that's the right place for new BTrieve modules. O.k., I settle on BTRIEVE::Native for the XS part. It'll implement BTRIEVE::Native::Call() which reads like

Re: BTRIEVE::*

2003-12-04 Thread Randy W. Sims
On 12/4/2003 3:50 PM, Tim Bunce wrote: On Thu, Dec 04, 2003 at 11:42:07AM +0100, Steffen Goeldner wrote: Randy W. Sims wrote: Maybe DBMS::BTrieve::??? That looks good! But that's a new namespace. The horse has well and truly bolted on the db module namespace issue. They're all over

BTRIEVE::*

2003-12-03 Thread Steffen Goeldner
Hi, I'm about to release two modules: BTRIEVE::XS BTRIEVE::API The first, BTRIEVE::XS, is a simple XS wrapper module for Btrieve's single function API. I.e., you can call Btrieve's C function BTRCALL() in perl as BTRIEVE::XS::Call(). The second, BTRIEVE::API, provides methods for common

Re: BTRIEVE::*

2003-12-03 Thread Nicholas Clark
On Wed, Dec 03, 2003 at 05:12:07PM +0100, Steffen Goeldner wrote: Hi, I'm about to release two modules: BTRIEVE::XS BTRIEVE::API The first, BTRIEVE::XS, is a simple XS wrapper module for Btrieve's single function API. I.e., you can call Btrieve's C function BTRCALL() in perl

Re: BTRIEVE::*

2003-12-03 Thread Randy W. Sims
On 12/3/2003 11:12 AM, Steffen Goeldner wrote: Hi, I'm about to release two modules: BTRIEVE::XS BTRIEVE::API The first, BTRIEVE::XS, is a simple XS wrapper module for Btrieve's single function API. I.e., you can call Btrieve's C function BTRCALL() in perl as BTRIEVE::XS::Call(). The second