-
Notifications
You must be signed in to change notification settings - Fork 123
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Inconsistent error messages #176
Comments
Tcl 8.6 does seems to be moving to towards standardising on "unknown or ambiguous subcommand ...", thus not differentiating between unknown and ambiguous, so that is a reasonable choice. Although there are still situations where other wording is used. % lsort -xxx z % interp z |
#194 harmonizes some error messages related to |
The https://github.com/msteveb/jimtcl/tree/cmd-register branch resolves this by consistently using JimCmdUsage() to report usage errors.
|
string z => "bad option "z": must be bytelength, ... , or trimright"
info z => "bad subcommand "z": must be alias, ... , or version"
file z => "file, unknown command "z": should be atime, ... , isfile"
If a cmd with subcmds is created in C:
cmd z => "cmd, ambiguous command "z": should be something, ..., other"
Which form should I use for my programs?
The text was updated successfully, but these errors were encountered: