head 1.2;
access;
symbols
RPM_4_2_1:1.1.1.5
RPM_4_2:1.1.1.5
RPM_4_1_1:1.1.1.5
RPM_4_1:1.1.1.4
RPM_4_0_5:1.1.1.3
RPM_4_0_4:1.1.1.2
RPM_4_0_3:1.1.1.1
RPM:1.1.1;
locks; strict;
comment @# @;
1.2
date 2008.01.02.09.55.38; author rse; state dead;
branches;
next 1.1;
commitid z4cpSiAhOCXk5PLs;
1.1
date 2001.07.23.20.45.38; author rse; state Exp;
branches
1.1.1.1;
next ;
1.1.1.1
date 2001.07.23.20.45.38; author rse; state Exp;
branches;
next 1.1.1.2;
1.1.1.2
date 2002.01.08.00.30.12; author rse; state Exp;
branches;
next 1.1.1.3;
1.1.1.3
date 2003.01.18.13.49.03; author rse; state Exp;
branches;
next 1.1.1.4;
1.1.1.4
date 2001.07.23.20.09.19; author rse; state Exp;
branches;
next 1.1.1.5;
1.1.1.5
date 2003.01.18.14.05.00; author rse; state Exp;
branches;
next ;
desc
@@
1.2
log
@remove the ancient RPM 4.2.1 source tree copy
@
text
@
Berkeley DB Reference Guide: Tcl API programming notes
- Berkeley DB Reference Guide:
- Tcl API
|
  
|
Tcl API programming notes
The Tcl API closely parallels the Berkeley DB programmatic interfaces. If you
are already familiar with one of those interfaces, there will not be many
surprises in the Tcl API.
Several pieces of Berkeley DB functionality are not available in the Tcl API.
Any of the functions that require a user-provided function are not
supported via the Tcl API. For example, there is no equivalent to the
DB->set_dup_compare or the DB_ENV->set_errcall
methods.
Copyright Sleepycat Software
@
1.1
log
@Initial revision
@
text
@d1 1
a1 1
@
1.1.1.1
log
@Import: RPM 4.0.3
@
text
@@
1.1.1.2
log
@Import: RPM 4.0.4
@
text
@d1 1
a1 1
@
1.1.1.3
log
@Import: RPM 4.0.5
@
text
@d2 1
a2 1
a3 1
@
1.1.1.4
log
@Import: RPM 4.1
@
text
@d2 1
a2 1
d4 1
@
1.1.1.5
log
@Import: RPM 4.1.1
@
text
@d2 1
a2 1
a3 1
@