-Time-stamp: <2005-08-02 10:24:25 blp>
+Time-stamp: <2006-02-17 22:06:31 blp>
Get rid of need for GNU diff in `make check'.
Get rid of need for file name canonicalization.
-Use getsubopt()?
-
-Format specifier and missing values code needs to be rewritten for lowered
-crappiness.
+Format specifier code needs to be rewritten for lowered crappiness.
CROSSTABS needs to be re-examined.
Add compression to casefiles.
-There needs to be another layer onto the lexer, which should probably be
-entirely rewritten anyway. The lexer needs to read entire *commands* at a
-time, not just a *line* at a time. It also needs to support arbitrary putback,
-probably by just backing up the "current position" in the command buffer.
-
Scratch variables should not be available for use following TEMPORARY.
-Details of N OF CASES, SAMPLE, FILTER, PROCESS IF, TEMPORARY, etc., need to be
-checked against the documentation. See notes on these at end of file for a
-start.
-
Check our results against the NIST StRD benchmark results at
strd.itl.nist.gov/div898/strd
PostScript driver should emit thin lines, then thick lines, to optimize time
and space.
-New functions? var_name_or_label(), tab_value_or_label()
-
Should be able to bottom-justify cells. It'll be expensive, though, by
requiring an extra metrics call.
Support multi-line titles on tables. (For the first page only, presumably.)
-Rewrite the convert_F() function in data-out.c to be nicer code.
-
In addition to searching the source directory, we should search the current
directory (for data files). (Yuck!)
Fix som_columns().
-Has glob.c been pared down enough?
-
Improve interactivity of output by allowing a `commit' function for a page.
This will also allow for infinite-length pages.
The manual: add text, add index entries, add examples.
-The inline file should be improved: There should be *real* detection of whether
-it is used (in dfm.c:cmd_begin_data), not after-the-fact detection.
-
Figure out a stylesheet for messages displayed by PSPP: i.e., what quotation
marks around filenames, etc.
-New SET subcommand: OUTPUT. i.e., SET OUTPUT="filename" to send output to that
-file; SET OUTPUT="filename"(APPEND) to append to that file; SET OUTPUT=DEFAULT
-to reset everything. There might be a better approach, though--think about it.
-
From Zvi Grauer <z.grauer@csuohio.edu> and <zvi@mail.ohio.net>:
1. design of experiments software, specifically Factorial, response surface
6. Categorical data analsys ?
-IDEAS
------
-
-In addition to an "infinite journal", we should keep a number of
-individual-session journals, pspp.jnl-1 through pspp.jnl-X, renaming and
-deleting as needed. All of the journals should have date/time comments.
-
-Qualifiers for variables giving type--categorical, ordinal, ...
-
-Analysis Wizard
-
-Consider consequences of xmalloc(), fail(), hcf() in interactive
-use:
-a. Can we safely just use setjmp()/longjmp()?
-b. Will that leak memory?
-i. I don't think so: all procedure-created memory is either
-garbage-collected or globally-accessible.
-ii. But you never know... esp. w/o Checker.
-c. Is this too early to worry? too late?
-
-Need to implement a shared buffer for funny functions that require relatively
-large permanent transient buffers (1024 bytes or so), that is, buffers that are
-permanent in the sense that they probably shouldn't be deallocated but are only
-used from time to time, buffers that can't be allocated on the stack because
-they are of variable and unpredictable but usually relatively small (usually
-line buffers). There are too many of these lurking around; can save a sizeable
-amount of space at very little overhead and with very little effort by merging
-them.
-
-Clever multiplatform GUI idea (due partly to John Williams): write a GUI in
-Java where each statistical procedure dialog box could be downloaded from the
-server independently. The statistical procedures would run on (the/a) server
-and results would be reported through HTML tables viewed with the user's choice
-of web browsers. Help could be implemented through the browser as well.
-
-HOWTOs
-------
-
MORE NOTES/IDEAS/BUGS
---------------------
* Document Record::
* Machine int32 Info Record::
* Machine flt64 Info Record::
-* Auxilliary Variable Parameter Record::
+* Auxiliary Variable Parameter Record::
* Long Variable Names Record::
* Miscellaneous Informational Records::
* Dictionary Termination Record::
indicates 8-bit ASCII, 4 indicates DEC Kanji.
@end table
-@node Machine flt64 Info Record, Auxilliary Variable Parameter Record, Machine int32 Info Record, Data File Format
+@node Machine flt64 Info Record, Auxiliary Variable Parameter Record, Machine int32 Info Record, Data File Format
@section Machine @code{flt64} Info Record
There must be no more than one machine @code{flt64} info record per
The value used for LOWEST in missing values.
@end table
-@node Auxilliary Variable Parameter Record, Long Variable Names Record, Machine flt64 Info Record, Data File Format
-@section Auxilliary Variable Parameter Record
+@node Auxiliary Variable Parameter Record, Long Variable Names Record, Machine flt64 Info Record, Data File Format
+@section Auxiliary Variable Parameter Record
-There must be no more than one auxilliary variable parameter record per
+There must be no more than one auxiliary variable parameter record per
system file. This record must follow the variable
records and precede the dictionary termination record.
The size @code{int32}. Always set to 4.
@item int32 count;
-The total number of bytes in @code{aux_params} divided by 3.
+The total number of records in @code{aux_params}, multiplied by 3.
@item struct aux_params aux_params[];
An array of @code{struct aux_params}. The order of the elements corresponds
@item int32 measure
The measurement type of the variable:
@table @asis
-@item 0
-Nominal Scale
@item 1
-Ordinal Scale
+Nominal Scale
@item 2
+Ordinal Scale
+@item 3
Continuous Scale
@end table
-@node Long Variable Names Record, Miscellaneous Informational Records, Auxilliary Variable Parameter Record, Data File Format
+@node Long Variable Names Record, Miscellaneous Informational Records, Auxiliary Variable Parameter Record, Data File Format
@section Long Variable Names Record
There must be no more than one long variable names record per
projects / pspp-builds.git / commitdiff