Re: [Xen-devel] xm create option parsing..

[Steven Hand <Steven.Hand@xxxxxxxxxxxx>]

>Steven Hand wrote:
>
>> As far as I can see, "xm create -c vmid=1" will create a domain and
>> attach to its console while "xm create vmid=1 -c" won't. 
>> 
>> Any reason for this? The option parsing routines xm/opts.py and 
>> xm/create.py seems substantial enough.
>> 
>
>It's an artifact of getopt - it stops parsing options at
>the first non-option. So
>
>xm create -c vmid=1
>
>sets the -c option, whereas
>
>xm create vmid=1 -c
>
>doesn't.
>
>It think there's a getopt flag to process options anywhere
>in the args, but this is a problem for a multicommand like xm
>that has its own options as well as subcommand options.
>
>Basically options (-x, --x) have to precede args.

Ok - we should probably note this somewhere, particularly as I guess
that many folks will be familiar with the gnu getopt style which 
doesn't assume that there are no more options once a non-option 
argument is seen. 


cheers, 

S.