Non-ASCII Characters - E1.20 RDM (Remote Device Management) Protocol Forums

hamish · July 22nd, 2016

Not sure I'm quite on the same page, the standard, as it is written, may not be entierly expicit.

If as is suggested, null termination is generally acceptable, then I would expect the relevant text to read something akin to

Text fields shall either terminate based on Parameter Data Length or when a NULL is encountered.

IMO The standard states that string lengths shall be PDL determined,
this being the correct approach. It then ads a caveat with the statement however, determining the appropriate treatment, in the case of a null character being encountered.

By using PDL length determined strings, there is no doubt that the implimentation will be compliant with the standard.

July 22nd, 2016	#8
hamish Member Join Date: Apr 2009 Location: Dartmoor, Devon, England Posts: 56	Not sure I'm quite on the same page, the standard, as it is written, may not be entierly expicit. If as is suggested, null termination is generally acceptable, then I would expect the relevant text to read something akin to Text fields shall either terminate based on Parameter Data Length or when a NULL is encountered. IMO The standard states that string lengths shall be PDL determined, this being the correct approach. It then ads a caveat with the statement however, determining the appropriate treatment, in the case of a null character being encountered. By using PDL length determined strings, there is no doubt that the implimentation will be compliant with the standard. __________________ ______________________________________________ Hamish Dumbreck