Mark Johnson wrote:
> 2. My compile still has three warnings (see below).
> a. Are these warnings significant?
> b. Why am I getting them? (I've seen very few postings which mention
> compile errors or warnings)
>
> Here are the warnings:
> [root@oldbox]# cd /usr/src/diald-0.99.1
> [root@oldbox]# make
> ...
> timer.c: In function `validate_function':
> timer.c: 87: warning: comparison of distinct pointer types lacks a cast
> timer.c: 88: warning: comparison of distinct pointer types lacks a cast
> ...
> proxy_dev.c: In function `proxy_dev_init':
> proxy_dev.c: 146: `d' might be used uninitialized in this function
> ...
Did you uncomment the warnings-enabled cc definition in the make file? When I did
so I got a hell of a lot more warnings than that. But this sort of warning is
*usually* harmless. I'm not advocating writing code so loosely defined as to cause
this type of warning though. There are circumstances where you might want to
ignore pointer type checking in order to achieve generality or avoid a useless
conversion routine. But some say it's better to bite the bullet and avoid
ambiguity. I *usually* take the latter view. It's certainly hard to defend the
number of warnings I saw myself. Maybe there's something wrong with my library and
kernel header files?
Naughty boy Mike! Warnings Bad!
--
[EMAIL PROTECTED] Ralph Clark, Virgo Solutions Ltd (UK)
__ _
/ / (_)__ __ ____ __ * Powerful * Flexible * Compatible * Reliable *
/ /__/ / _ \/ // /\ \/ / *Well Supported * Thousands of New Users Every Day*
/____/_/_//_/\_,_/ /_/\_\ The Cost Effective Choice - Linux Means Business!
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
