On Fri, May 4, 2012 at 3:21 PM, Francois Gouget fgouget@free.fr wrote:
On Fri, 4 May 2012, Julian Rüger wrote:
Hi Francois and wine-devel,
while we're at it, shouldn't these
"Advertise a product:\n" "\t/j[u|m] package [/t transform] [/g languageid]\n" "Apply a patch:\n" "\t/p patch_package [property]\n" "\t/p patch_package /a package [property]\n"
also be put in curly brackets?
Like this:
\t/j[u|m] {package} [/t transform] ... \t/p {patch_package} [property]\n ...
My understanding is that for msiexec the curly brackets are only used to enclose cases where there is two or more alternatives: {a|b|c}. With {required parameter} being an exception to the rule, maybe because it in fact represents a list.
It would be nice if all of Wine's tools used the same conventions for the usage messages.
The msiexec conventions look sane to me: [ ] for optional and { } for mandatory parameters (*only* when a choice/list is involved). It's also what's used in other wine commands "/?" results (e.g. 'start', 'ipconfig', 'regedit', etc.).
Frédéric