public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Mikael Åsberg" <mikas493@student.liu.se>
To: <cygwin@cygwin.com>
Subject: Where did the output go and question regarding return values of getopt_long()
Date: Sun, 19 Dec 2004 15:15:00 -0000	[thread overview]
Message-ID: <006d01c4e5dd$7e4bda90$0200a8c0@mindcooler> (raw)

Hello, consider this c++-function:

void
handle_command_line(int argc,
                    char* const argv[],
                    bool& verbose,
                    vector<string>& numbers)
{
   const int id_numbers = 4711;
   const int id_verbose = 4712;
   const int id_help = 4713;

   const option long_options[] =
   {
      {"numbers", 1, NULL, id_numbers},
      {"verbose", 0, NULL, id_verbose},
      {"help", 0, NULL, id_help},
      {NULL, 0, NULL, 0}
   };

   const char* const short_options = "";

   int c = 0;

   while((c = getopt_long(
             argc,
             argv,
             short_options,
             long_options,
             NULL)) != -1)
   {
      switch(c)
      {
         cout << "c = " << c << endl; /* Never shown on screen... */

         case id_numbers:
         {
            cout << "Calling extract_numbers() with " << optarg << endl;

            extract_numbers(optarg, numbers);

            break;
         }
         case id_verbose:
         {
            cout << "Setting verbose = true" << endl;

            verbose = true;

            break;
         }
         case id_help:
         {
            cout << "TODO: Add short description regarding usage here." << 
endl;

            exit(EXIT_SUCCESS);
         }
         /* c seems to equal '?' for missing parameter as well... */
         case ':':
         {
            cerr << "Missing parameter." << endl;

            break;
         }
         /* Only triggers for unknown options beginning with -- */
         case '?':
         {
            cerr << "Ignoring unknown option." << endl;

            break;
         }
         default:
         {
            /* Throw exception? */
            cerr << "Should not be reached." << endl;
         }
      }
   }
}

My first question is about the
cout << "c = " << c << endl;
inside the switch. I never see this output, why? I tried writing the output 
to a file as well but that file was empty when the program finished. All 
other "output-statements" are displayed just fine in this function (and the 
rest of the program).

And my second questions is why does getopt_long() return '?' for the error 
when an option requires an argument but none was supplied? I thought that it 
would return ? for unknown option and return : for missing required 
parameters, but it seems to return ? for both those errors (but it ouputs 
the correct diagnostic).

I'm using latest offical cygwin, all relevant packages up-to-date. Running 
fully-updated winxp pro.

Thanks for any replies 



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

             reply	other threads:[~2004-12-19 15:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-19 15:15 Mikael Åsberg [this message]
2004-12-19 19:43 ` Larry Hall
2004-12-19 20:26 Mikael Åsberg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='006d01c4e5dd$7e4bda90$0200a8c0@mindcooler' \
    --to=mikas493@student.liu.se \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).