Re: [Factor-talk] Executing words on data farther up the stack

2008-08-21 Thread Eduardo Cavazos
Glenn Tarcea wrote: > Thanks for the suggestion! If I did this could I have multiple > databases open? That is, if my constructor was and I did that > twice, could I associate a variable with each instance? Sure, no problem. The idea is that the words in your library would operate on the db ha

Re: [Factor-talk] Executing words on data farther up the stack

2008-08-21 Thread Glenn Tarcea
Hi Ed, Thanks for the suggestion! If I did this could I have multiple databases open? That is, if my constructor was and I did that twice, could I associate a variable with each instance? Thanks, Glenn On Aug 21, 2008, at 10:21 PM, Eduardo Cavazos wrote: V. Glenn Tarcea wrote: I've

Re: [Factor-talk] Executing words on data farther up the stack

2008-08-21 Thread Eduardo Cavazos
V. Glenn Tarcea wrote: > I've been working on an interface to BerkeleyDB for Factor. Hi Glenn, An approach worth exploring is where you keep the bdb object in a variable. Ed - This SF.Net email is sponsored by the Moblin Y

Re: [Factor-talk] Executing words on data farther up the stack

2008-08-21 Thread Glenn Tarcea
Why doesn't bdb-open create a new berkleydb object and return it on the stack? I've been debating what the proper thing to do here is. That will help, but I'll still end up with calls where floats to the bottom of the stack. >r >r [ dbenv>> ] [ db>> ] bi r> r> You can use 2dip here.

Re: [Factor-talk] Executing words on data farther up the stack

2008-08-21 Thread Slava Pestov
On Thu, Aug 21, 2008 at 3:39 PM, V. Glenn Tarcea <[EMAIL PROTECTED]> wrote: > Hi, > > > > I've been working on an interface to BerkeleyDB for Factor. > Cool! Say I have a tuple to hold my BerkeleyDB data like DB_ENV, DB, etc…. When I > need to make a call I often end up with a stack that has th

[Factor-talk] Executing words on data farther up the stack

2008-08-21 Thread V. Glenn Tarcea
Hi, I've been working on an interface to BerkeleyDB for Factor. One thing I've noticed as I've worked through this is a common idiom like the following: Say I have a tuple to hold my BerkeleyDB data like DB_ENV, DB, etc.. When I need to make a call I often end up with a stack that has the b