Chris's Wiki :: blog/programming/LibraryWarnings Commentshttps://utcc.utoronto.ca/~cks/space/blog/programming/LibraryWarnings?atomcommentsDWiki2009-03-27T09:10:43ZRecent comments in Chris's Wiki :: blog/programming/LibraryWarnings.From 83.145.208.36 on /blog/programming/LibraryWarningstag:CSpace:blog/programming/LibraryWarnings:22df42dfc6ce355e3b4af627fd99d58cf3dfc573From 83.145.208.36<div class="wikitext"><p>Right on.</p>
<p>I have pondered with the same issue with few libraries I have worked on.</p>
<p>As usual, effective solutions are not novel but go far back: I really believe that the best solution is the good-old "errno"-type solution in a local context, perhaps accompanied by strongly #ifdef'd debugging messages. This should really be in some ABC of programming.</p>
<p>Programmers are not stupid and with proper documentation the question always boils down to "if you misuse the library, you burn". Handholding and over-verbosity is never a solution for a library, and indeed GTK is a <em>prima facie</em> example on what <em>not to do</em> in this context.</p>
<p>- j.</p>
</div>2009-03-27T09:10:43Z