-Time-stamp: <2006-04-15 18:11:46 blp>
+Time-stamp: <2006-05-06 11:38:03 blp>
-Get rid of need for GNU diff in `make check'.
+Procedure processing:
+
+* Should not need temporary casefile in the common case.
+
+* LAG need not be as much of a special case.
-Get rid of need for file name canonicalization.
+* Push FILTER, N OF CASES out of procedure.c.
+
+* Change sources into state machines?
+
+Get rid of need for GNU diff in `make check'.
Format specifier code needs to be rewritten for lowered crappiness.
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.
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
3. Write case to replacement active file.
4. Execute temporary transformations. If these drop the case, stop.
5. Post-TEMPORARY N OF CASES. If we have already analyzed N cases, stop.
-6. FILTER, PROCESS IF. If these drop the case, stop.
+6. FILTER. If this drops the case, stop.
7. Pass case to procedure.
Ugly cases:
because AGGREGATE creates its own case sink and writes to it in step 7. Also,
TEMPORARY has no effect and we just cancel it. Regardless of direction of
output, we should not implement AGGREGATE through a transformation because that
-will fail to honor FILTER, PROCESS IF, N OF CASES.
+will fail to honor FILTER, N OF CASES.
ADD FILES: Essentially an input program. It silently cancels unclosed LOOPs
and DO IFs. If the active file is used for input, then runs EXECUTE (if there
* Before TEMPORARY, selection is permanent. After TEMPORARY,
selection stops after a procedure.
-PROCESS IF
-
- * Always selects cases sent to the procedure.
-
- * No effect on cases sent to sink.
-
- * Always stops after a procedure.
-
SPLIT FILE
* Ignored by AGGREGATE. Used when procedures write matrices.
* RENAME VARIABLES is invalid after TEMPORARY.
- * WEIGHT, SPLIT FILE, N OF CASES, FILTER, PROCESS IF apply only to
+ * WEIGHT, SPLIT FILE, N OF CASES, FILTER apply only to
the next procedure when used after TEMPORARY.
WEIGHT
projects / pspp-builds.git / blobdiff