1 files changed, 34 insertions, 14 deletions
diff --git a/xsd/doc/pregenerated/xsd.1 b/xsd/doc/pregenerated/xsd.1
index f74a3b0..580ac78 100644
--- a/xsd/doc/pregenerated/xsd.1
+++ b/xsd/doc/pregenerated/xsd.1
@@ -1,7 +1,7 @@
 .\" Process this file with
 .\" groff -man -Tascii xsd.1
 .\"
-.TH XSD 1 "January 2022" "XSD 4.2.0-b.4"
+.TH XSD 1 "January 2023" "XSD 4.2.1-a.0"
 .SH NAME
 xsd \- W3C XML Schema to C++ Compiler
 .\"
@@ -119,12 +119,15 @@ if any, should appear after the corresponding
 .
 .IP "\fB--std\fR \fIversion\fR"
 Specify the C++ standard that the generated code should conform to\. Valid
-values are \fBc++98\fR (default) and \fBc++11\fR\.
+values are \fBc++98\fR, \fBc++11\fR (default), \fBc++14\fR, \fBc++17\fR,
+\fBc++20\fR, and \fBc++23\fR\.
 
 The C++ standard affects various aspects of the generated code that are
 discussed in more detail in various mapping-specific documentation\. Overall,
 when C++11 is selected, the generated code relies on the move semantics and
 uses \fBstd::unique_ptr\fR instead of deprecated \fBstd::auto_ptr\fR\.
+Currently, there is no difference between the C++11 and the later standards
+modes\.
 
 When the C++11 mode is selected, you normally don't need to perform any extra
 steps other than enable C++11 in your C++ compiler, if required\. The XSD
@@ -381,7 +384,8 @@ Generate \fBmake\fR dependency information\. This option triggers the creation
 of the \fB\.d\fR file containing the dependencies of the generated files on
 the main schema file as well as all the schema files that it includes/imports,
 transitively\. This dependency file is then normally included into the main
-\fBmakefile\fR to implement automatic dependency tracking\.
+\fBmakefile\fR to implement automatic dependency tracking\. See also the
+\fB--dep-*\fR options\.
 
 Note also that automatic dependency generation is not supported in the
 file-per-type mode (\fB--file-per-type\fR)\. In this case, all the generated
@@ -402,8 +406,12 @@ directory prefixes\. If you require multiple targets, then you can specify
 them as a single, space-separated argument or you can repeat this option
 multiple times\.
 .IP "\fB--dep-suffix\fR \fIsuffix\fR"
-Use the provided \fIsuffix\fR instead of the default \fB\.d\fR to construct
-the name of the dependency file\.
+Use \fIsuffix\fR instead of the default \fB\.d\fR to construct the name of the
+dependency file\. See also \fB--dep-file\fR\.
+.IP "\fB--dep-file\fR \fIpath\fR"
+Use \fIpath\fR as the generated dependency file path instead of deriving it
+from the input file name\. Write the dependency information to \fBstdout\fR if
+\fIpath\fR is \fB-\fR\. See also \fB--dep-regex\fR\.
 .IP "\fB--dep-regex\fR \fIregex\fR"
 Use the provided expression to construct the name of the dependency file\.
 \fIregex\fR is a Perl-like regular expression in the form
@@ -577,9 +585,14 @@ option is primarily useful when trying to minimize the amount of object code
 that is linked to an executable by packaging compiled generated code into a
 static (archive) library\.
 .IP "\fB--file-list\fR \fIfile\fR"
-Write a list of generated C++ files to \fIfile\fR\. This option is primarily
-useful in the file-per-type compilation mode (\fB--file-per-type\fR) to create
-a list of generated C++ files, for example, as a makefile fragment\.
+Write a list of generated C++ files to \fIfile\fR or to \fBstdout\fR if
+\fIfile\fR is \fB-\fR\. This option is primarily useful in the file-per-type
+compilation mode (\fB--file-per-type\fR) to create a list of generated C++
+files, for example, as a makefile fragment\.
+.IP "\fB--file-list-only\fR"
+Only write the list of C++ files that would be generated without actually
+generating them\. This option only makes sense together with
+\fB--file-list\fR\.
 .IP "\fB--file-list-prologue\fR \fItext\fR"
 Insert \fItext\fR at the beginning of the file list\. As a convenience, all
 occurrences of the \fB\en\fR character sequence in \fItext\fR are replaced
@@ -1292,7 +1305,6 @@ namespace http://www.example.com/xmlns/my
 .br
 .RE
 
-
 The compiler has a number of predefined mapping rules that can be
 presented as the following map files. The string-based XML Schema
 built-in types are mapped to either
@@ -1303,6 +1315,14 @@ depending on the character type selected with the
 .B --char-type
 option
 .RB ( char
+by default). The binary XML Schema types are mapped to either
+.B std::unique_ptr<xml_schema::buffer>
+or
+.B std::auto_ptr<xml_schema::buffer>
+depending on the C++ standard selected with the
+.B --std
+option
+.RB ( c++11
 by default).
 
 .RS
@@ -1382,13 +1402,13 @@ namespace http://www.w3.org/2001/XMLSchema
   QName xml_schema::qname;
 .br
 
-  base64Binary std::auto_ptr<xml_schema::buffer>
+  base64Binary std::[unique|auto]_ptr<xml_schema::buffer>
 .br
-               std::auto_ptr<xml_schema::buffer>;
+               std::[unique|auto]_ptr<xml_schema::buffer>;
 .br
-  hexBinary std::auto_ptr<xml_schema::buffer>
+  hexBinary std::[unique|auto]_ptr<xml_schema::buffer>
 .br
-            std::auto_ptr<xml_schema::buffer>;
+            std::[unique|auto]_ptr<xml_schema::buffer>;
 .br
 
   date xml_schema::date;
@@ -1471,7 +1491,7 @@ and exit with non-zero exit code.
 .SH BUGS
 Send bug reports to the xsd-users@codesynthesis.com mailing list.
 .SH COPYRIGHT
-Copyright (c) 2005-2022 Code Synthesis Tools CC.
+Copyright (c) 2005-2023 Code Synthesis.
 
 Permission is granted to copy, distribute and/or modify this
 document under the terms of the GNU Free Documentation License,