> Provided that the questions of compatibility are answered positively ...
For PVXS, field name conformance is only enforced for locally defined types. I've added a test to check that an "in-valid" field name can be decoded, and re-encoded (eg. by a PVA gateway). Some non-conformant names won't be accessible locally though.
> Provided that the questions of compatibility are answered positively ...
For PVXS, field name conformance is only enforced for locally defined types. I've added a test to check that an "in-valid" field name can be decoded, and re-encoded (eg. by a PVA gateway). Some non-conformant names won't be accessible locally though.
https:/ /github. com/mdavidsaver /pvxs/commit/ 2ab0d662bf3f74f 32915d0e07383d8 c30217fdd5
I don't have time at present to do this testing for pvDataCPP/ AccessCPP, pvDataJava/ AccessJava, or Kay's new PVA.