Il 12/11/2013 10:58, Igor Mammedov ha scritto: > extending QemuOpts to parsing ±opts format, seems like good workaround > above problem. But I was under impression that general movement was to convert > custom formats to canonical format "prop=value".
I think the general movement is to convert things to QemuOpts. As long as all compound options use QemuOpts, they are consistent and any syntactic sugar will apply to all in the same way. I, for one, can never remember if it is =on, =true, =yes (and interestingly =no works but =yes doesn't). So I welcome a new completely different syntax that doesn't have this problem. :) Paolo
