Garrett Smith wrote:
Given that, I suggest moving forward: Test, then document those methods as having special behavior. Do this not by a null->value mapping, but by documenting the method's algorithm in simple terms. e.g. "if X is not a string, throw an error"
But giving a (per-method) mapping means that the algorithm can then be machine-generated from the IDL, which is an interoperability win: less chance of a mistake being made.
So why are you opposed to having such per-method mappings, as needed? -Boris
