diff options
| author | Explorer09 <explorer09@gmail.com> | 2017-07-18 22:37:19 +0800 |
|---|---|---|
| committer | Will Estes <westes575@gmail.com> | 2017-08-24 08:34:23 -0400 |
| commit | fb731ac0221e1866534dfe072b84b8af7a5d88f3 (patch) | |
| tree | cb7c3345fa23aac5ca84da235d88da2728b2831d /src/scanopt.c | |
| parent | d64a5263cfcd490a6a96b2d6c018fa40f1ed558a (diff) | |
scanner: remove BASENAME(); don't strip path from program_name
There's no technical need of stripping path from program_name. I think
the users should be fine if they see the path they use to invoke flex
is diagnostic messages and help texts.
Yes, users will see "Usage: ../flex [OPTIONS]..." now if they invoke
flex with the path "../flex".
The --version output has been changed so that the name field will be
always "flex" or "flex++". If the flex program has been renamed to
"lex" (for compatibility or other reason) this will allow identifying
the implementation name ("flex"). (And it's a recommended practice in
GNU Coding Standards)
Diffstat (limited to 'src/scanopt.c')
| -rw-r--r-- | src/scanopt.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/scanopt.c b/src/scanopt.c index 3162e9f..7745c11 100644 --- a/src/scanopt.c +++ b/src/scanopt.c @@ -247,7 +247,7 @@ int scanopt_usage (scanopt_t *scanner, FILE *fp, const char *usage) fprintf (fp, "%s\n", usage); } else { - fprintf (fp, _("Usage: %s [OPTIONS]...\n"), BASENAME(s->argv[0]) ); + fprintf (fp, _("Usage: %s [OPTIONS]...\n"), s->argv[0]); } fprintf (fp, "\n"); |