On C++ generated code,  __isset is set to true in the read function
for the fields that have been received, however it is not looked at at
all by the write function which always writes all fields regardless of
the __isset value.

What is the reasoning behind this asymmetry? Is __isset intended only
to cater for the receiving side, in particular for the use case in
which the receiver is of a different software version than the sender?

Reply via email to