when implemented using the current interface it creates a complex code, getting a SCPI_Parameter first, then implementing two cases based on whether the parameter type is SCPI_TOKEN_PROGRAM_MNEMONIC for SCPI_ParamToChoice or SCPI_ParamToFloat. Additional validation code to match ranges also necessary.
An example SCPI command:
CONFigure:VOLTage:DC {0.2|2|20|AUTO}
when implemented using the current interface it creates a complex code, getting a SCPI_Parameter first, then implementing two cases based on whether the parameter type is SCPI_TOKEN_PROGRAM_MNEMONIC for SCPI_ParamToChoice or SCPI_ParamToFloat. Additional validation code to match ranges also necessary.
However, a much simpler hack is possible:
The ask is to be able to express choices as numerics without forcibly overwriting the parameter type.