pvget json error

The version of yajl that comes with Base 7.0.6.1 and later can generate JSON5 which handles infinities and NaN values, but it looks like the pvAccess code in pvget isn't enabling that option in the print formatter. Applying the following patch to modules/pvData should fix it:

diff --git a/src/factory/printer.cpp b/src/factory/printer.cpp
index 928fc4f..31f7116 100644
--- a/src/factory/printer.cpp
+++ b/src/factory/printer.cpp
@@ -404,6 +404,9 @@ std::ostream& operator<<(std::ostream& strm, const PVStructure::Formatter& forma
     if(format.xfmt==PVStructure::Formatter::JSON) {
         JSONPrintOptions opts;
         opts.multiLine = false;
+#if EPICS_VERSION_INT>=VERSION_INT(7,0,6,1)
+ opts.json5 = true;
+#endif
         printJSON(strm, format.xtop, format.xshow ? *format.xshow : BitSet().set(0), opts);
         strm<<'\n';
         return strm;

Given that this is actually a bug against pvDataCPP I have filed an issue against that module on GitHub referring to this bug report: https://github.com/epics-base/pvDataCPP/issues/92

Thank you - the patch fixes the issue for me.

This fix has been merged into the pvDataCPP module and will appear in the next EPICS 7.0.x release, thanks for the report.

I've just noticed that enabling json5 changes the output from {"value":22.0 ...} to {value:22.0 ...}, i.e. removes the quotes.

Could that be a problem for other users?

Does that work okay for you though?

Quotes are optional in JSON-5 for map keys that meet the requirements for an identifier, so the yajl generator checks map keys and only uses quotes when they're needed. A JSON-5 parser that accepts NaN values should also accept unquoted keys. An older JSON parser would not allow them, but then it should also reject Infinity and NaN as numeric values.

I did suggest in my GitHub PR the alternative solution of providing a separate "-M json5" mode, but that idea would require rather more work. If unquoted keys are a problem though I would raise that suggestion again and also have the strict JSON generator convert NaN and Infinity values into strings.

Yes, it is fine for me - I didn't even notice the change at first!