From 7eff406b9c978ab146f4e81f79391b4f79381f29 Mon Sep 17 00:00:00 2001 From: Ben Pfaff Date: Thu, 21 Mar 2024 06:44:03 -0700 Subject: [PATCH] REPEATING DATA: Remove documentation for unimplemented command. This command once had a buggy implementation, which was removed, but the documentation remained. Thanks to Frans Houweling for reporting the inconsistency. --- doc/data-io.texi | 83 -------------------------------------------------------- 1 file changed, 83 deletions(-) diff --git a/doc/data-io.texi b/doc/data-io.texi index 23cc7e51a..81d446f65 100644 --- a/doc/data-io.texi +++ b/doc/data-io.texi @@ -52,7 +52,6 @@ actually be read until a procedure is executed. * PRINT EJECT:: Eject the current page then print. * PRINT SPACE:: Print blank lines. * REREAD:: Take another look at the previous input line. -* REPEATING DATA:: Multiple cases on a single line. * WRITE:: Display values in write formats. @end menu @@ -1125,88 +1124,6 @@ file. @xref{INSERT}, for information on supported encodings. Issuing @code{REREAD} multiple times will not back up in the data file. Instead, it will re-read the same line multiple times. -@node REPEATING DATA -@section REPEATING DATA -@vindex REPEATING DATA - -@display -REPEATING DATA - /STARTS=@var{start}-@var{end} - /OCCURS=@var{n_occurs} - /FILE='@var{file_name}' - /LENGTH=@var{length} - /CONTINUED[=@var{cont_start}-@var{cont_end}] - /ID=@var{id_start}-@var{id_end}=@var{id_var} - /@{TABLE,NOTABLE@} - /DATA=@var{var_spec}@dots{} - -where each @var{var_spec} takes one of the forms - @var{var_list} @var{start}-@var{end} [@var{type_spec}] - @var{var_list} (@var{fortran_spec}) -@end display - -@cmd{REPEATING DATA} parses groups of data repeating in -a uniform format, possibly with several groups on a single line. Each -group of data corresponds with one case. @cmd{REPEATING DATA} may only be -used within an @cmd{INPUT PROGRAM} structure (@pxref{INPUT PROGRAM}). -When used with @cmd{DATA LIST}, it -can be used to parse groups of cases that share a subset of variables -but differ in their other data. - -The @subcmd{STARTS} subcommand is required. Specify a range of columns, using -literal numbers or numeric variable names. This range specifies the -columns on the first line that are used to contain groups of data. The -ending column is optional. If it is not specified, then the record -width of the input file is used. For the inline file (@pxref{BEGIN -DATA}) this is 80 columns; for a file with fixed record widths it is the -record width; for other files it is 1024 characters by default. - -The @subcmd{OCCURS} subcommand is required. It must be a number or the name of a -numeric variable. Its value is the number of groups present in the -current record. - -The @subcmd{DATA} subcommand is required. It must be the last subcommand -specified. It is used to specify the data present within each repeating -group. Column numbers are specified relative to the beginning of a -group at column 1. Data is specified in the same way as with @cmd{DATA LIST -FIXED} (@pxref{DATA LIST FIXED}). - -All other subcommands are optional. - -FILE specifies the file to read, either a file name as a string or a -file handle (@pxref{File Handles}). If FILE is not present then the -default is the last file handle used on @cmd{DATA LIST} (lexically, not in -terms of flow of control). - -By default @cmd{REPEATING DATA} will output a table describing how it will -parse the input data. Specifying @subcmd{NOTABLE} will disable this behavior; -specifying TABLE will explicitly enable it. - -The @subcmd{LENGTH} subcommand specifies the length in characters of each group. -If it is not present then length is inferred from the @subcmd{DATA} subcommand. -LENGTH can be a number or a variable name. - -Normally all the data groups are expected to be present on a single -line. Use the @subcmd{CONTINUED} command to indicate that data can be continued -onto additional lines. If data on continuation lines starts at the left -margin and continues through the entire field width, no column -specifications are necessary on @subcmd{CONTINUED}. Otherwise, specify the -possible range of columns in the same way as on STARTS. - -When data groups are continued from line to line, it is easy -for cases to get out of sync through careless hand editing. The -@subcmd{ID} subcommand allows a case identifier to be present on each line of -repeating data groups. @cmd{REPEATING DATA} will check for the same -identifier on each line and report mismatches. Specify the range of -columns that the identifier will occupy, followed by an equals sign -(@samp{=}) and the identifier variable name. The variable must already -have been declared with @cmd{NUMERIC} or another command. - -@cmd{REPEATING DATA} should be the last command given within an -@cmd{INPUT PROGRAM}. It should not be enclosed within a @cmd{LOOP} -structure (@pxref{LOOP}). Use @cmd{DATA LIST} before, not after, -@cmd{REPEATING DATA}. - @node WRITE @section WRITE @vindex WRITE -- 2.11.4.GIT