On 11/24/05, <b class="gmail_sendername">Carl Worth</b> <<a href="mailto:cworth@cworth.org">cworth@cworth.org</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
No. C coders are not meant to call _get_status repeatedly. What<br>happens is that if _get_status would return an error status then<br>basically all of that object's functions become NOOPs. That is, it is<br>still safe to call functions on that object and defer the _get_status
<br>error checking until a convenient time.<br><br>If binding to a language that supports exceptions it probably does<br>make sense to call _get_status after each call and throw exceptions.<br><br>-Carl<br><br>
</blockquote></div><br>
I don't know if anyone else agrees with me, but I think the idea of
having the wrapper be configurable with a policy to handle the errors
is highly attractive.<br>
The alternative would be to have a bool checkForErrors and check if
before checking and handling errors. This would imply run-time
overhead, while using the policies would not.<br>
<br>
What do you think ?<br>
<br>
Rui Pires<br>