Judson Valeski wrote:
> Should checking the return value be enough to protect me from a null
> aString being returned?
No. They're semantically quite different, and describe different
conditions. The result code will tell you about the operation of the
method, which might fail for a whole number of reasons. It's up to the
caller to decide, based on the semantics of the method being called,
whether it considers a null out param to be an error.
We should not conflate the two. There is no bug here.
Mike
