[Pspp-cvs] pspp ./TODO src/data/casefile.c

[Ben Pfaff]

CVSROOT:        /cvsroot/pspp
Module name:    pspp
Branch:         
Changes by:     Ben Pfaff <address@hidden>      06/04/26 22:15:43

Modified files:
        .              : TODO 
        src/data       : casefile.c 

Log message:
        Update to-do list.

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/pspp/pspp/TODO.diff?tr1=1.34&tr2=1.35&r1=text&r2=text
http://cvs.savannah.gnu.org/viewcvs/pspp/pspp/src/data/casefile.c.diff?tr1=1.7&tr2=1.8&r1=text&r2=text

Patches:
Index: pspp/TODO
diff -u pspp/TODO:1.34 pspp/TODO:1.35
--- pspp/TODO:1.34      Sun Apr 16 01:11:44 2006
+++ pspp/TODO   Wed Apr 26 22:15:43 2006
@@ -1,9 +1,7 @@
-Time-stamp: <2006-04-15 18:11:46 blp>
+Time-stamp: <2006-04-26 15:15:36 blp>
 
 Get rid of need for GNU diff in `make check'.
 
-Get rid of need for file name canonicalization.
-
 Format specifier code needs to be rewritten for lowered crappiness.
 
 CROSSTABS needs to be re-examined.
@@ -12,39 +10,21 @@
 Kruskal-Wallis on NPAR TESTS and for Spearman and the Johnkheere trend test (in
 other procedures).
 
-lex_token_representation() should take a buffer to fill.
-
-Make valgrind --leak-check=yes --show-reachable=yes work.
-
 Add NOT_REACHED() macro.
 
-Add compression to casefiles.
-
 Scratch variables should not be available for use following TEMPORARY.
 
 Check our results against the NIST StRD benchmark results at
 strd.itl.nist.gov/div898/strd
 
-In debug mode hash table code should verify that collisions are reasonably low.
-
 Storage of value labels on disk is inefficient.  Invent new data structure.
 
-Add an output flag which would cause a page break if a table segment could fit
-vertically on a page but it just happens to be positioned such that it won't.
-
 Fix spanned joint cells, i.e., EDLEVEL on crosstabs.stat.
 
-Cell footnotes.
-
-Should be able to bottom-justify cells.  It'll be expensive, though, by
-requiring an extra metrics call.
-
 SELECT IF should be moved before other transformations whenever possible.  It
 should only be impossible when one of the variables referred to in SELECT IF is
 created or modified by a previous transformation.
 
-The manual: add text, add index entries, add examples.
-
 Figure out a stylesheet for messages displayed by PSPP: i.e., what quotation
 marks around filenames, etc.
 
@@ -66,9 +46,6 @@
 
    6. Categorical data analsys ?
 
-MORE NOTES/IDEAS/BUGS
----------------------
-
 Sometimes very wide (or very tall) columns can occur in tables.  What is a good
 way to truncate them?  It doesn't seem to cause problems for the ascii or
 postscript drivers, but it's not good in the general case.  Should they be
Index: pspp/src/data/casefile.c
diff -u pspp/src/data/casefile.c:1.7 pspp/src/data/casefile.c:1.8
--- pspp/src/data/casefile.c:1.7        Tue Apr 25 00:41:12 2006
+++ pspp/src/data/casefile.c    Wed Apr 26 22:15:43 2006
@@ -111,6 +111,8 @@
    casefile_destroy().  This function will also destroy any
    remaining casereaders. */
 
+/* FIXME: should we implement compression? */
+
 /* In-memory cases are arranged in an array of arrays.  The top
    level is variable size and the size of each bottom level array
    is fixed at the number of cases defined here.  */