X-Git-Url: https://git.saurik.com/bison.git/blobdiff_plain/95612cfa608188fc323ed3f8560cc6aea953ff32..573a6cd3568911ec7a698daea60fa24f36088cd2:/doc/bison.texinfo

diff --git a/doc/bison.texinfo b/doc/bison.texinfo
index f9e18e23..edfe35c0 100644
--- a/doc/bison.texinfo
+++ b/doc/bison.texinfo
@@ -268,7 +268,6 @@ Invoking Bison
 * Bison Options::     All the options described in detail,
                         in alphabetical order by short options.
 * Option Cross Key::  Alphabetical list of long options.
-* VMS Invocation::    Bison command syntax on @acronym{VMS}.
 
 Frequently Asked Questions
 
@@ -5906,7 +5905,6 @@ will produce @file{output.c++} and @file{outfile.h++}.
 * Bison Options::     All the options described in detail,
                         in alphabetical order by short options.
 * Option Cross Key::  Alphabetical list of long options.
-* VMS Invocation::    Bison command syntax on @acronym{VMS}.
 @end menu
 
 @node Bison Options
@@ -6098,34 +6096,6 @@ the corresponding short option.
 @end example
 @end ifinfo
 
-@node VMS Invocation
-@section Invoking Bison under @acronym{VMS}
-@cindex invoking Bison under @acronym{VMS}
-@cindex @acronym{VMS}
-
-The command line syntax for Bison on @acronym{VMS} is a variant of the usual
-Bison command syntax---adapted to fit @acronym{VMS} conventions.
-
-To find the @acronym{VMS} equivalent for any Bison option, start with the long
-option, and substitute a @samp{/} for the leading @samp{--}, and
-substitute a @samp{_} for each @samp{-} in the name of the long option.
-For example, the following invocation under @acronym{VMS}:
-
-@example
-bison /debug/name_prefix=bar foo.y
-@end example
-
-@noindent
-is equivalent to the following command under @acronym{POSIX}.
-
-@example
-bison --debug --name-prefix=bar foo.y
-@end example
-
-The @acronym{VMS} file system does not permit filenames such as
-@file{foo.tab.c}.  In the above example, the output file
-would instead be named @file{foo_tab.c}.
-
 @c ================================================= Invoking Bison
 
 @node FAQ