Rename a Boolean flag variable to reflect the non-default behavior.

This makes it slightly clearer, from code inspection, what the -C flag
does.  The default behavior is to continue; -C cause capinfos to stop,
rather than continue, after an open failure.

Change-Id: I8bc67ce61c5d828c7f0ed87ee397ef994ff99aa4
Reviewed-on: https://code.wireshark.org/review/31621
Reviewed-by: Guy Harris <guy@alum.mit.edu>
This commit is contained in:
Guy Harris 2019-01-19 13:55:45 -08:00
parent 4b6dbf4baf
commit 0c89d8c33a
1 changed files with 3 additions and 3 deletions

View File

@ -95,7 +95,7 @@
* failure.
*/
static gboolean continue_after_wtap_open_offline_failure = TRUE;
static gboolean stop_after_wtap_open_offline_failure = FALSE;
/*
* table report variables
@ -1561,7 +1561,7 @@ main(int argc, char *argv[])
break;
case 'C':
continue_after_wtap_open_offline_failure = FALSE;
stop_after_wtap_open_offline_failure = TRUE;
break;
case 'A':
@ -1679,7 +1679,7 @@ main(int argc, char *argv[])
if (!wth) {
cfile_open_failure_message("capinfos", argv[opt], err, err_info);
overall_error_status = 2; /* remember that an error has occurred */
if (!continue_after_wtap_open_offline_failure)
if (stop_after_wtap_open_offline_failure)
goto exit;
}