-Time-stamp: <2006-02-17 22:06:31 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.
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.
-
-Use AFM files instead of Groff font files, and include AFMs for our default
-fonts with the distribution.
-
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.
-
-PostScript driver should emit thin lines, then thick lines, to optimize time
-and space.
-
-Should be able to bottom-justify cells. It'll be expensive, though, by
-requiring an extra metrics call.
-
-Perhaps instead of the current lines we should define the following line types:
-null, thin, thick, double. It might look pretty classy.
-
-Perhaps thick table borders that are cut off by a page break should decay to
-thin borders. (i.e., on a thick bordered table that's longer than one page,
-but narrow, the bottom border would be thin on the first page, and the top and
-bottom borders on middle pages.)
-
-Support multi-line titles on tables. (For the first page only, presumably.)
-
-In addition to searching the source directory, we should search the current
-directory (for data files). (Yuck!)
-
-Fix line-too-long problems in PostScript code, instead of covering them up.
-setlinecap is *not* a proper solution.
-
-Fix som_columns().
-
-Improve interactivity of output by allowing a `commit' function for a page.
-This will also allow for infinite-length pages.
-
-Implement thin single lines, should be pretty easy now.
-
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.
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
for instance through a wide PRINT request--try time-date.stat with a narrow
ascii page or with the postscript driver on letter size paper.)
-NULs in input files break the products we're replacing: although it will input
-them properly and display them properly as AHEX format, it truncates them in A
-format. Also, string-manipulation functions such as CONCAT truncate their
-results after the first NUL. This should simplify the result of PSPP design.
-Perhaps those ugly a_string, b_string, ..., can all be eliminated.
-
From Moshe Braner <mbraner@nessie.vdh.state.vt.us>: An idea regarding MATCH
FILES, again getting BEYOND the state of SPSS: it always bothered me that if I
have a large data file and I want to match it to a small lookup table, via