Christian Couder [off-list ref] writes:
quoted
quoted
quoted
+ pr-infos = pr-info | pr-infos ";" pr-info
[...]
quoted
quoted
I wonder if it would instead be useful to have <pr-infos> first write
out how many <pr-info>s it contains, and then write out each <pr-info>
separated by a NUL byte, so that none of the files in the <pr-info>
itself are restricted in what characters they can use.
I am not sure how NUL bytes would interfere with the pkt-line.[c,h] code though.
...
However I still think that capabilities have been using a simple text
format for now which works well, and that it's better to respect that
format and not introduce complexity in it if it's not necessary.
Yup, especially when we are in control of what goes into "pr-info",
I do not see much reason to go binary. It helps debuggability
greatly to stay in text format when you can.
Thanks.