Bruno Haible <[EMAIL PROTECTED]> writes: > A linker warning with a one or two line text is better than a link error > because > > - We can enable a link warning even for cases where 90% of the uses of the > functions are ok, such as
For cases like these, I'd rather not have a warning, as there are too many false alarms. > - A link errors aborts the "make" process, a link warning doesn't. Hmm, we seem to be on different wavelengths here. I want the 'make' to fail if someone is using a function that should not be used. For example, in the string module, I want 'make' to fail if any module uses ctime, since it's asking for trouble in portable code (it has undefined behavior with out-of-range time stamps). I suppose someone could write code that carefully bounds the time stamps and then uses ctime; such code can "#undef ctime" if it really wants to. Perhaps we're talking about different levels of severity here?
