diff --git a/docs/README b/docs/README index 8ab9d97..8e99542 100644 --- a/docs/README +++ b/docs/README @@ -2,4 +2,4 @@ To generate the manual from the docbook xml you need and xslt processor and an xsl file that defines the output. For example: -xsltproc --stringparam html.stylesheet style.css /usr/share/sgml/docbook/xsl-stylesheets-1.61.3/xhtml/docbook.xsl manual.xml > manual.html +xsltproc --stringparam html.stylesheet style.css /Users/mes/software/docbook-xsl-1.71.1/xhtml/docbook.xsl manual.xml > manual.html diff --git a/docs/manual.html b/docs/manual.html index 6d90fc4..28dc348 100644 --- a/docs/manual.html +++ b/docs/manual.html @@ -615,6 +615,7 @@ class MyOutput : public StdOutput { cerr << "My special failure message for: " << endl << e.what() << endl; + exit(1); } virtual void usage(CmdLineInterface& c) @@ -647,7 +648,9 @@ See test4.cpp in the examples directory for the fu example. NOTE: if you supply your own Output object, we will not delete it in the CmdLine destructor. This could lead to a (very small) memory leak if you don't take care of the object -yourself. +yourself. Also note that the failure method is +now responsible for exiting the application (assuming that is the desired +behavior).

I don't want the --help and --version switches to be created automatically...

Help and version information is useful for nearly all command line applications and as such we generate flags that provide those options automatically. diff --git a/docs/manual.xml b/docs/manual.xml index e96acf0..9ef5841 100644 --- a/docs/manual.xml +++ b/docs/manual.xml @@ -800,6 +800,7 @@ class MyOutput : public StdOutput { cerr << "My special failure message for: " << endl << e.what() << endl; + exit(1); } virtual void usage(CmdLineInterface& c) @@ -832,7 +833,9 @@ See test4.cpp in the examples directory for the full example. NOTE: if you supply your own Output object, we will not delete it in the CmdLine destructor. This could lead to a (very small) memory leak if you don't take care of the object -yourself. +yourself. Also note that the failure method is +now responsible for exiting the application (assuming that is the desired +behavior).