Re: Compile warnings

On Fri, 2003-03-07 at 23:18, Joost wrote:


> Is the reason that noone is answering just that nobody knows, or is there
> something wrong with my question?

Warnings are just that: warnings. They point out to you that you did
something which might not turn out like you intended, or that you
possible did something which is valid C/C++ code but looks suspicious. 

If the compiled code runs as expected you're free to ignore any warning.
If it breaks code you should start looking in the directions the warning
points you.

Take this one:

kern_compat.h:216: warning: `DECLARE_MUTEX' redefined

It's probably a preprocessor-macro. Which was already defined elsewhere.
If both amount to the same code, nothing will break. You just define the
same macro twice. If they differ, and you rely on one macro, but the
other one is the last one defined your headers will not contain the
definitions the code assumes, and your compiler will give an error, or
the linker will, or, possibly, you will get errors runtime. The warning
will tell you that something happened to DECLARE_MUTEX and you should
investigate.

Your question doesn't belong on this list, by the way. If you want more
detailed information, or an answer from somebody who can actually write
code (I can't, for one) you're better off at comp.lang.c, comp.lang.c++
or the various FAQ's: http://www.google.com/search?q=C+programming+FAQ

-- 
ruben <[email protected]>
_______________________________________________
vortex mailing list
[email protected]
http://www.scyld.com/mailman/listinfo/vortex