From 2bd0d88360ebc1c2ca8346891a3b4ab62a8270d4 Mon Sep 17 00:00:00 2001 From: Moshe Zadka Date: Wed, 11 Apr 2001 07:33:08 +0000 Subject: Fixing bug 405999 -- clarifying differences between Python's getopt and GNU getopt -- Python is like classical UNIX getopt. --- Doc/lib/libgetopt.tex | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/Doc/lib/libgetopt.tex b/Doc/lib/libgetopt.tex index 563460b..c96c3cf 100644 --- a/Doc/lib/libgetopt.tex +++ b/Doc/lib/libgetopt.tex @@ -25,6 +25,10 @@ recognize, with options that require an argument followed by a colon (\character{:}; i.e., the same format that \UNIX{} \cfunction{getopt()} uses). +\strong{Note:} Unlike GNU \cfunction{getopt()}, after a non-option +argument, all further arguments are considered also non-options. +This is similar to the way non-GNU \UNIX{} systems work. + \var{long_options}, if specified, must be a list of strings with the names of the long options which should be supported. The leading \code{'-}\code{-'} characters should not be included in the option -- cgit v0.12