| Ticket UUID: | f0f876c141139439586fa28de774889055df7edb | ||
| Title: | Inconsistent terminology in error messages: option vs. switch | ||
| Type: | Bug | Created on: | 2014-06-13 00:51:36 |
| Submitter: | andy | Assigned to: | dkf |
| Subsystem: | 45. Parsing and Eval | Severity: | Minor |
| Priority: | 5 Medium | Last modified: | 2014-06-17 14:30:41 |
| Status: | Closed | Closed by: | dkf |
| Resolution: | Fixed | Closed on: | 2014-06-17 14:30:41 |
| Version: | 39da5e7464431971934e73e300f4d1c8a8cd72a6 | ||
| Description: | ||||
Sometimes it's a bad switch, other times it's a bad option. Here's one example of the inconsistency: % regsub -help a b bad switch "-help": must be -all, -nocase, -expanded, -line, -linestop, -lineanchor, -start, or -- % switch -asdf a b bad option "-asdf": must be -exact, -glob, -indexvar, -matchvar, -nocase, -regexp, or -- Other kinds of inconsistencies exist, but I want to address only one at a time. | ||||