From af91f7a2ff8e0760293fe38724c1c589bb0ff2a6 Mon Sep 17 00:00:00 2001 From: Ben Pfaff Date: Mon, 4 Jul 2005 05:06:39 +0000 Subject: [PATCH] Fix comment. --- src/casefile.c | 23 +++++++++-------------- 1 file changed, 9 insertions(+), 14 deletions(-) diff --git a/src/casefile.c b/src/casefile.c index f7d171f7..706a6b93 100644 --- a/src/casefile.c +++ b/src/casefile.c @@ -61,17 +61,13 @@ independent position in the casefile. Casereaders may only move forward. They cannot move - backward to arbitrary records or seek randomly. (In the - future, the concept of a "casemark" will be introduced - to allow a limited form of backward seek, but this has - not yet been implemented.) - - Cloning casereaders is possible, but no one has had a - need for it yet, so it is not implemented. + backward to arbitrary records or seek randomly. + Cloning casereaders is possible, but it is not yet + implemented. Use casefile_get_reader() to create a casereader for - use in phase 2. This also transitions from phase 2 to - phase 3. Calling casefile_mode_reader() makes the same + use in phase 2. This also transitions from phase 1 to + phase 2. Calling casefile_mode_reader() makes the same transition, without creating a casereader. Use casereader_read(), casereader_read_xfer(), or @@ -83,9 +79,8 @@ also read with casereaders in this phase, but the ability to create new casereaders is curtailed. - In this phase, casereaders could still be cloned, and - casemarks could still be used to seek backward (given - that we eventually implement these functionalities). + In this phase, casereaders could still be cloned (once + we eventually implement cloning). To transition from phase 1 or 2 to phase 3 and create a casereader, call casefile_get_destructive_reader(). @@ -96,8 +91,8 @@ more casereaders may be created with casefile_get_reader() or casefile_get_destructive_reader(). (If cloning of - casereaders or casemarks were implemented, they would - still be possible.) + casereaders were implemented, it would still be + possible.) The purpose of the limitations applied to casereaders in phase 3 is to allow in-memory casefiles to fully -- 2.30.2