On Wednesday, August 25, 2010 11:55:07 Diego Elio Pettenò wrote:
> What this bug is about is rather the kind of errors that I've commented
> on in [1], [2] and [3] which is that they _may_ be related to macros or
> functions that are not declared/defined by the current set of library
> dependencies, and would then lead to unresolved undefined symbols, and
> thus, to runtime failure.

or:
 - the return value is larger than an "int", and thus possibly truncated
 - the func requires 3 args, but user passes some other number, and compiler 
cannot flag it
 - the user passes args in the incorrect order and the compiler cant check it
-mike