Hello @j123b567, have you ever considered making the number of significant digits returned by SCPI_ResultDouble configurable? Or perhaps creating another function (e.g. "SCPI_ResultDoubleN(scpi_t * context, double val, size_t prec)") that provides a parameter for precision?
I am using scpi-parser in an instrument that uses doubles to represent a value with 8 significant digits, and some of the stakeholders on my team mentioned that the 15 digits that are returned are less than ideal, given the extra 7 meaningless digits in a result that is returned at a rate of 100 rdgs/sec. I figured maybe you had thought about this before, and if not, I wondered if you'd be open to that sort of feature.
Hello @j123b567, have you ever considered making the number of significant digits returned by SCPI_ResultDouble configurable? Or perhaps creating another function (e.g. "SCPI_ResultDoubleN(scpi_t * context, double val, size_t prec)") that provides a parameter for precision?
I am using scpi-parser in an instrument that uses doubles to represent a value with 8 significant digits, and some of the stakeholders on my team mentioned that the 15 digits that are returned are less than ideal, given the extra 7 meaningless digits in a result that is returned at a rate of 100 rdgs/sec. I figured maybe you had thought about this before, and if not, I wondered if you'd be open to that sort of feature.