Re: [Qemu-devel] [Qemu-block] Non-flat command line option argument syntax

2017-02-05 Thread Max Reitz
On 04.02.2017 10:51, Markus Armbruster wrote: > "Richard W.M. Jones" writes: > >> On Thu, Feb 02, 2017 at 08:42:33PM +0100, Markus Armbruster wrote: >>> There's also the -drive file=json:... syntax. It's a bad fit for >>> QemuOpts, because QemuOpts and JSON fight for the comma. I'd show you >>>

Re: [Qemu-devel] [Qemu-block] Non-flat command line option argument syntax

2017-02-04 Thread Markus Armbruster
Max Reitz writes: > I like both JSON and dot syntax. But I like them differently in > different places. > > I love JSON when it's in some file where I can turn out syntax > highlighting and let my $EDITOR match brackets and braces. > > I hate JSON when it's on the command line. You have to escape

Re: [Qemu-devel] [Qemu-block] Non-flat command line option argument syntax

2017-02-04 Thread Markus Armbruster
Max Reitz writes: > On 03.02.2017 08:50, Markus Armbruster wrote: >> "Dr. David Alan Gilbert" writes: >> >>> * Markus Armbruster (arm...@redhat.com) wrote: = Introduction = >>> >>> >>> = Structured option argument syntax = == JSON == The obvious way to provid

Re: [Qemu-devel] [Qemu-block] Non-flat command line option argument syntax

2017-02-03 Thread Max Reitz
I like both JSON and dot syntax. But I like them differently in different places. I love JSON when it's in some file where I can turn out syntax highlighting and let my $EDITOR match brackets and braces. I hate JSON when it's on the command line. You have to escape, you get strings in strings, an

Re: [Qemu-devel] [Qemu-block] Non-flat command line option argument syntax

2017-02-03 Thread Max Reitz
On 03.02.2017 08:50, Markus Armbruster wrote: > "Dr. David Alan Gilbert" writes: > >> * Markus Armbruster (arm...@redhat.com) wrote: >>> = Introduction = >>> >> >> >> >>> = Structured option argument syntax = >>> >>> == JSON == >>> >>> The obvious way to provide the expressiveness of JSON on the