On 23/01/2020 11:42, Jan Beulich wrote: > In order to avoid permanently having to ask that no new command line > options using underscores be introduced (albeit I'm likely to still make > remarks), and in order to also allow extending the use of hyphens to > pre-existing ones, introduce custom comparison functions treating both > characters as matching. > > Signed-off-by: Jan Beulich <jbeul...@suse.com> > --- > v2: Rename to opt_str{,n}cmp(). Don't use the new function for comapring > against "no-" in parse_params(). Add comment to cdiff().
Personally, I think this is a bad idea and should not be continued. Yes - it is irritating needing to remember whether an option is spelled with hyphen or underscore, but that is nothing compared to the pain for users, who will have less bleeding edge version of Xen where the different really matters. Having one consistent behaviour across all versions of Xen is of far more value to people than trying to fix a few wonky corner cases for developers benefit. ~Andrew _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel