| Ticket UUID: | 861801 | |||
| Title: | Add a new option parser routine tailored for functions | |||
| Type: | RFE | Version: | None | |
| Submitter: | certgen | Created on: | 2003-12-17 17:27:07 | |
| Subsystem: | cmdline | Assigned To: | andreas_kupries | |
| Priority: | 5 Medium | Severity: | ||
| Status: | Closed | Last Modified: | 2013-07-04 17:24:54 | |
| Resolution: | Not Applicable Here | Closed By: | ||
| Closed on: | ||||
| Description: |
Hey, I find the cmdline library particularly useful for script writing. I usually define a custom getFunctionsOpts routine that is a slight twist on the getKnownOptions routine (no support for -?/-h/-help) for new Tcl projects. The attached cmdline.tcl file contains the getFunctionOptions procedure -- I would like to submit this as a feature request for the next release of tcllib. Thanks for all the great utils! -Ian Chesal | |||
| User Comments: |
certgen added on 2004-03-04 03:59:04:
Logged In: YES user_id=82268 The attached code doesn't do anything if unexpected options are encountered. It just shuffles them into the $argv variable like it does with non-option arguments. It's much easier to use this in proc's than the other parser because you don't want procs to print help information if they get bad options -- you want the proc to decide what to do, usually thats just returning an error message. andreas_kupries added on 2004-03-03 08:47:54: Logged In: YES user_id=75003 I will have a look, but no promises. Why is the removal of the -h support so important ? Was it replaced with something else ? Or just an error message ? certgen added on 2003-12-18 00:27:07: File Added - 70863: cmdline.tcl | |||
Attachments:
- cmdline.tcl [download] added by certgen on 2003-12-18 00:27:07. [details]