X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=doc%2Flanguage.texi;h=78d38acdc6f0813fe2e1666fa7ddfa8b5bb69c31;hb=c0d0b8039a3cd836398a76a0a884d6166ed761e0;hp=50e8f646aea4aaac7f3efc9955b78318d8d49a55;hpb=5c3291dc396b795696e94f47780308fd7ace6fc4;p=pspp-builds.git

diff --git a/doc/language.texi b/doc/language.texi
index 50e8f646..78d38acd 100644
--- a/doc/language.texi
+++ b/doc/language.texi
@@ -3,10 +3,6 @@
 @cindex language, PSPP
 @cindex PSPP, language
 
-@note{PSPP is not even close to completion.
-Only a few statistical procedures are implemented.  PSPP
-is a work in progress.}
-
 This chapter discusses elements common to many PSPP commands.
 Later chapters will describe individual commands in detail.
 
@@ -116,8 +112,7 @@ significant inside strings.
 
 Strings can be concatenated using @samp{+}, so that @samp{"a" + 'b' +
 'c'} is equivalent to @samp{'abc'}.  Concatenation is useful for
-splitting a single string across multiple source lines. The maximum
-length of a string, after concatenation, is 255 characters.
+splitting a single string across multiple source lines.
 
 Strings may also be expressed as hexadecimal, octal, or binary
 character values by prefixing the initial quote character by @samp{X},
@@ -152,11 +147,6 @@ punctuator only as the last character on a line (except white space).
 When it is the last non-space character on a line, a period is not
 treated as part of another token, even if it would otherwise be part
 of, e.g.@:, an identifier or a floating-point number.
-
-Actually, the character that ends a command can be changed with
-@cmd{SET}'s ENDCMD subcommand (@pxref{SET}), but we do not recommend
-doing so.  Throughout the remainder of this manual we will assume that
-the default setting is in effect.
 @end table
 
 @node Commands
@@ -184,9 +174,7 @@ by a forward slash (@samp{/}).
 There are multiple ways to mark the end of a command.  The most common
 way is to end the last line of the command with a period (@samp{.}) as
 described in the previous section (@pxref{Tokens}).  A blank line, or
-one that consists only of white space or comments, also ends a command
-by default, although you can use the NULLINE subcommand of @cmd{SET}
-to disable this feature (@pxref{SET}).
+one that consists only of white space or comments, also ends a command.
 
 @node Syntax Variants
 @section Variants of syntax.
@@ -212,9 +200,9 @@ new command, which allows for visual indentation of a command without
 that command being considered part of the previous command. 
 The period terminating the end of a command is optional but recommended.
 
-In interactive mode, each command must  either be terminated with a period,
-or an empty line must follow the command.
-The use of (@samp{+} and @samp{@minus{}} as continuation characters is not
+In interactive mode, each command must be terminated with a period
+or by a blank line.
+The use of @samp{+} and @samp{@minus{}} as continuation characters is not
 permitted.
 
 @node Types of Commands
@@ -379,9 +367,7 @@ spaces.
 Variables, whether numeric or string, can have designated
 @dfn{user-missing values}.  Every user-missing value is an actual value
 for that variable.  However, most of the time user-missing values are
-treated in the same way as the system-missing value.  String variables
-that are wider than a certain width, usually 8 characters (depending on
-computer architecture), cannot have user-missing values.
+treated in the same way as the system-missing value.
 
 For more information on missing values, see the following sections:
 @ref{Variables}, @ref{MISSING VALUES}, @ref{Expressions}.  See also the