On Tue, Oct 18, 2016 at 10:36:54AM +0200, Miroslav Lichvar wrote: > On Mon, Oct 17, 2016 at 08:46:22PM +0000, Keller, Jacob E wrote: > > Is it possible to update configuration somehow to allow passing a > > variable as "empty" which will assign it to empty string, and then > > update your prefix code flow so that it correctly works and doesn't add > > a " " when the string is actually empty? Not sure how easy it would be > > to fix that or not. > > I think that would be an easy fix. > > Another possibility is to allow double-quotes around strings in the > config. If the first and last character of the string was ", they > would be removed. The default value for logging_prefix would simply be > "". If someone is already using quoted strings in userDescription, > productDescription or revisionData, they would have to have an extra > pair of quotes around them. > > What do you think?
I don't think it is worth the effort to support null strings in the config file. This opens up a whole can of worms of quoting and escaping issues. We already don't have every option as a default anyhow. Let's keep it simple for now, and say "omit option from config for null". Thanks, Richard ------------------------------------------------------------------------------ Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today. http://sdm.link/xeonphi _______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
